Release Notes

1.20.1 2026-09-22

Fixed

• The scan no longer freezes the screen while it prepares the photo. Rendering and encoding a 12-megapixel camera frame was happening on the main thread, so for 80ms or more nothing could redraw — including the progress spinner that is meant to show the scan is working (#80). Measured stall: 80ms before, under 25ms after, and that is on a fast Mac; a phone was worse. The scan takes the same time; it stops looking stuck while it happens.

1.20.0 2026-09-22

Fixed

• Odometer scanning is dramatically faster. Every scan was uploading a photo of every single car in your garage so the AI could match the dashboard by sight. With twelve cars that is 10.26 MB per scan, and a phone's upload speed is a fraction of its download speed however strong the signal looks — which is where the reported ~45 seconds went (#78). Those photos are gone. The app identifies the car from each one's last odometer reading instead, which it was already sending as text and which is right essentially always. Measured on the same photo and a twelve-car garage: 10.26 MB → 0.78 MB, input tokens 59,749 → 4,367, and about 3 seconds of upload on a slow connection instead of 41. The reading itself is unchanged — benchmarking found the photos made no difference to accuracy on two separate corpora.
• A scan costs 2.3¢ instead of 30¢. Those reference photos were charged as image tokens — twelve of them at full size came to 59,749 input tokens per scan against 4,367 without, so at Opus 4.8's $5/MTok a scan cost 13× more than it does now. Settings has always estimated "~2–3¢" for an Opus scan; that estimate is accurate for the first time. For a scan a day, $109/year becomes $8.

Added

• Odometer scans now report where their time went (#78). A scan taking more than 10 seconds says so and names the stage responsible, and every scan logs a full stage-by-stage breakdown. The original report was impossible to diagnose from a description, and this is so the next one isn't.
• Kept scan-review samples now record the scan's duration, its stage breakdown, and which AI model read it, so a slow scan can be told apart from a wrong one.

Changed

• A car's reference photo is no longer used for anything. You can still set one and it is still stored, but nothing reads it — see #79.

1.19.1 2026-09-20

Fixed

• A mistyped odometer reading no longer skews a car's average MPG. The fuel-economy chart already ignored impossible figures so they wouldn't wreck it — but the average shown on the dashboard didn't, so a bad entry disappeared from the chart while still dragging the headline number. Worse, the chart looking normal made the average look trustworthy. On a four-fill history with one 10× typo the average read 153 MPG instead of 30; the EV equivalent read 1,398 MPGe instead of about 102. Both now ignore the same entries, from the same threshold. This does not yet tell you about a suspect entry — it's still silently excluded from both. That part is #72 and is waiting on a decision about a "filled the tank?" checkbox, which would prevent most of these at entry instead of flagging them afterwards.

1.19.0 2026-09-20

Changed

• The per-car fuel-economy chart is now spaced by fill-up, not by date. Fill-ups are unevenly spaced in time — a fortnight of commuting, then six weeks parked — and on a date axis those gaps dominated the picture while consecutive fills were squeezed together and hard to compare. Economy is a property of a tank rather than of a week, so each fill now gets an equal slot, oldest first. The axis labels still show when each fill happened, so nothing about the timeline is lost.

Fixed

• Two fill-ups on the same day are both visible now. On the old date axis they landed on the same position and the second was drawn underneath the first — so a second fill on one day simply wasn't there. This was the motivating bug behind the axis change rather than a side effect of it.

1.18.0 2026-09-20

Fixed

• A network blip can no longer produce a second, empty spreadsheet. On launch the app checks the workbook it remembers; that check treated any failure — a dropped connection, a Google outage, an expired token — the same as "the spreadsheet was deleted", and then went looking for one. Because Drive's file search is also eventually consistent and can briefly not list a file that exists, the two together could end in the app creating a fresh empty workbook while your real one sat in Drive. That presents as every car and every entry having vanished. Now only a genuine "not found" justifies making one, anything else is reported so you can retry, and an empty search is confirmed a second time before creating.
• Entries with no odometer reading no longer show "0 mi". An insurance payment logged without a reading was displaying as made at zero miles; it now says "no reading", shown lighter rather than in a different colour.
• A vehicle history document no longer tells the AI a car was bought at zero miles when the purchase odometer was never recorded — it says "not recorded" and asks it not to estimate annual mileage from the ownership period. Both facts were going into a document meant for a buyer.

Internal

• The Mac chart-typography test was branching on a compile-time platform check inside an iOS-only test target, so its Mac half never compiled and its expectations had drifted to sizes the code stopped using months ago. The sizes are now a pure function of "is this a Mac", so both platforms are checked from either one.
• digitRegion now has tests that run real text recognition over rendered digits and verify the crop lands on the half containing them — closing the gap where ADR-040 claimed a coordinate flip was covered when the test actually pinned its consumer.
• ADR-009, ADR-016 and ADR-018 corrected where they described intentions as facts, each dated with the version that made it true. ADR-048 records the rule. Tests 340 → 350.

1.17.1 2026-09-20

Fixed

• "Delete kept photos" no longer claims success when it fails. If removal failed, Settings said "Kept so far: 0" with the photos still on the device — and because the button only appears when the count is above zero, it also took away the only way to try again. The count now only resets when the files actually go.
• A large photo can no longer slip past the size limit the app applies before sending a scan. An optimisation added in 1.17.0 measured the image in points rather than pixels, so an image with a 2× scale factor could be sent at double the intended resolution. Not reachable from the camera, but the limit is there for a reason.
• Kept scan photos decide where to go by asking the store, not by checking which storage mode the app is in. Those can disagree, and when they did the photos would have gone back to being unnamed files — the bug 1.17.0 fixed.

Internal

• ADR-047 (a pixel budget is not a point budget); ADR-045 extended with CarStore.preservesFileNames and the failed-delete path. Tests 337 → 340.
• second-opinion reworked to make agreement expensive rather than its prose harsher: claim_check now demands a falsifier before a ruling and can answer "could not check", and the reviewer must name its weakest claim and where it would look for a defect it missed. Re-running the identical review took it from 0 findings to 2.

1.17.0 2026-09-20

Fixed

• A scan no longer refuses to fill in a reading just because the two readers disagree. The app cross-checks the AI against on-device recognition, and it was leaving the field empty whenever they differed — but the on-device reader is the weaker of the two, so it was vetoing perfectly good readings and making you retype them. Now it fills the field and tells you the other reading, and only withholds when something actually contradicts the number: the AI's own digit list not matching, or a reading with fewer digits than your last one.
• The digit-count check now uses the car you picked, not the car the scan guessed. Previously a correct low reading on a new car could be refused because a different car reads 128,456 — and the message quoted a number that car never had.
• Saving an entry no longer waits for the diagnostic upload. With "Keep my odometer scans" on, the entry sheet stayed open while two photos uploaded.
• Kept scans work properly on-device. In local mode the photos were being written as unnamed files with no folder and no way to find or delete them, while Settings said otherwise. They now go to a real folder with real names, and Settings has a "Delete kept photos" button that actually works.
• Kept scans record kilometres correctly. One field was being stored in miles while the rest were in your chosen unit, which made every kept sample wrong for anyone not using miles.
• A gas-pump scan no longer inherits the previous odometer photo, which filed the pump's number against the wrong picture.
• A scan photo is no longer re-processed four times, which on a 12-megapixel photo was enough memory pressure to matter on an older phone.
• The "Keep photos I correct" switch is now "Keep my odometer scans", because it keeps all of them — the correct ones are what show whether a change helped.

Internal

• ADR-044 (evidence of error withholds; absence of agreement warns), ADR-045 (a store method is not reusable until both implementations are read), ADR-046 (units are picked once and recorded with the value). ADR-040's test-coverage claim corrected. Tests 333 → 337. Two findings filed as #77 rather than guessed at.

1.16.0 2026-09-20

Added

• Settings → Improve Odometer Scanning. Off by default. Turn it on and each odometer photo you scan is kept in a “Scan Review” folder in your own Google Drive (or on the device in local mode), together with what the app read and what you actually saved. That gives the scanning something real to be measured against instead of sample pictures — which is what the last round of fixes was missing. Photos go nowhere else, and you can delete the folder whenever you like; nothing in the app reads it back. It keeps the ones it got right as well as the ones you corrected. That sounds like clutter and isn't: without them, a change can look like an improvement while quietly breaking readings that already worked.

Fixed

• A corrected car guess again learns from the whole dashboard photo. In 1.15.0 the new zoom-to-the-digits step meant that when you corrected which car a scan belonged to, the app stored a tight crop of the instrument cluster as that car's reference picture instead of the dashboard shot — leaving later scans trying to recognise a car from its gauges.

Internal

• ADR-043. Testing/odometer-bench/import-scan-review.py converts a downloaded Scan Review folder into a bench sample set. Tests 326 → 333.

1.15.0 2026-09-20

Fixed

• The photo is now zoomed to the numbers before it's sent. A pump display fills the frame, which is why pump scanning always worked. Your instrument cluster fills maybe a quarter of a dashboard photo, and after the app shrank the picture for upload the odometer digits were only about 20 pixels tall — too small to read reliably. The app now finds the cluster on-device, crops to it at full resolution, and sends that at higher detail. On test photos framed like real ones this went from 0 out of 6 correct to 6 out of 6.
• A reading the app isn't sure about is no longer filled in for you. It already ran a second, independent reader to cross-check — and when the two disagreed it said "double-check" and filled in the first one's answer anyway. Now it tells you both numbers and leaves the field for you. It also refuses a reading that has fewer digits than your last one, since an odometer can't lose a digit, and one where the AI's own digit-by-digit transcription doesn't match the number it reported.

Internal

• New Testing/odometer-bench/ — scores scanning against photos with known readings, and holds the measurements behind the above. Not in the app target.
• Removed a line from the AI prompt warning that photos "may be upside down". Measured over 40 calls on upright and rotated images, it changed nothing in either direction; the app already corrects orientation before sending.
• Three architecture decisions recorded: ADR-040 (crop to the digits before encoding), ADR-041 (a prompt may not describe a condition the pipeline has removed), ADR-042 (prefill a scan only when nothing contradicts it).
• Tests 315 → 326.

1.14.0 2026-09-17

Fixed

• A second charge at the same charger could vanish. Two charging entries for the same car, day, odometer and price but different kWh were treated as one duplicate row, and the second disappeared on every read — then a move to a new store made it permanent. Energy is part of what distinguishes two entries now, as is the "fuel added without being logged" flag.
• Dates edited in the spreadsheet could shift to the previous day. Once a date cell is formatted as a date, Sheets stores it as a plain day number — and those were read as UTC, which west of UTC is the day before. A entry dated the 1st came back as the last day of the previous month, moving it between months in the charts and reports. It now lands on the day it names.
• Changes queued for one Google account could sync into another. Queued changes deliberately survive a sign-out, so they aren't lost — but they weren't tagged with whose they were. Signing in with a different Google account replayed the first account's changes into the second account's spreadsheet. They're now held for the account that made them: sign back in and they sync, or Disconnect to discard, and the app tells you which account is waiting.
• One unreadable queued change no longer discards all of them. Unsynced changes were read all-or-nothing, so a single damaged one silently dropped the entire queue — the only copy of every change waiting to sync. Each is read on its own now, and if any can't be read the app says how many were lost instead of leaving you to discover it.
• Ticking off a reminder or a to-do no longer reverts an edit made elsewhere. A one-tap "done" sent the whole row from this device's copy, which can be up to 30 seconds old — so it could undo a title or note changed in the web version. It now writes only what being done actually changes.
• A photo or document uploaded while the app refreshed kept its file. A narrow timing window could blank the link between an entry and the file it had just uploaded, which then left the file stranded in your Drive when the entry was deleted.
• A deleted document's row goes before its file. The two happen as separate requests, and if the second was interrupted the old order left an entry pointing at a file that no longer existed — unopenable, forever. Reversed, an interruption leaves an unused file in Drive instead, which nothing has to look at.

Internal

• Five architecture decisions recorded: ADR-035 (a queued write belongs to one account and one record), ADR-036 (read stored collections element by element), ADR-037 (delete the row before the file), ADR-038 (a dedup key names every meaningful field), ADR-039 (a spreadsheet date cell is a calendar day).
• Tests 287 → 307. The Sheets test harness can now answer requests by URL, so a test about the order of requests can't pass or fail for the wrong reason.

1.13.0 2026-09-16

Fixed

• A decimal odometer reading was ten times too high. Typing 12345.6 — a trip meter, a km reading, or what a photo scan returns — stored 123456. The reading is what every mileage, MPG and cost-per-mile figure in the app is worked out from, so one entry threw off every chart, and the wrong number looked like real data rather than a mistake. Reminder due-mileage and repeat intervals had the same bug. All three now read the number you typed, including in locales that write 1250,5.
• An edit made while a change was still uploading could be thrown away. Renaming an entry that hadn't finished syncing showed as saved, then vanished when the earlier upload completed. The newer version now stays queued and goes out.
• Fixing that could have duplicated an upload. A photo or document whose entry stayed queued would have been uploaded a second time, leaving an orphan file in your Drive. The app now remembers the file it already uploaded and reuses it.
• A future update could have discarded your unsynced changes. Reminders and to-dos were the two records whose stored form couldn't tolerate a new field being added. Because unsynced changes and the offline cache are both read leniently, one unreadable field would have silently dropped the whole queue of changes waiting to sync — the only copy of them — rather than one field. Both now read tolerantly, like every other record already did.
• nan or inf no longer breaks a save. Both parse as real numbers in Swift, and neither can be written to JSON — so one in a cost, gallons or kWh field made the offline cache fail to save, with nothing shown in Google mode. Rejected now both when typed and when read from the spreadsheet, which is the likelier source: the sheet is a document you and the web version both edit.

Internal

• Running the test suite no longer writes to (or deletes from) the same on-device storage a development build uses. Tests get an isolated temporary directory.
• The column-ownership rule from 1.12.0 — a write only sends the columns it owns, so it can't clobber a value the web app set — is now pinned by tests across every combination, driven through the real Sheets code rather than a stand-in.
• Two new architecture decisions recorded: ADR-033 (the unsynced queue is the only copy of a change) and ADR-034 (one parser for every user-typed number).

1.12.0 2026-09-16

Fixed

• A save could overwrite or delete the wrong record. Every write found its row by id and then wrote to that row number. If the web app, your Mac, or you editing the sheet by hand removed a row above it in the meantime, everything shifted up and the write landed on a different entry — an edit overwrote its neighbour, a delete removed the wrong one, and the duplicate that was left behind was hidden on the next read. Writes now re-check the row is still the right one immediately before touching it, and abandon the write rather than guess.
• A failed request could delete a second row. Deletes are sent as a POST, and any failed request was automatically retried — so if the server applied the delete and then failed, the retry deleted the next row down. No second device needed; one bad connection was enough. Requests that create or remove something are no longer retried.
• Moving your data to Google could wipe rows added elsewhere. The move cleared the existing spreadsheet first, including anything the web version had added that this device had never seen — under a dialog promising nothing would be deleted. It now checks first and refuses, telling you what it found.
• A Google outage could throw away your offline edits. Edits made offline were dropped after five failed attempts, and a server error counted as an attempt — so a long outage deleted the very changes the queue exists to protect. Server errors and rate limits now keep their place in the queue.
• An edit could bring back something you deleted. If you deleted a car or entry on the web and your phone had an unsent edit to it, the edit re-created it. The app now knows the difference between "this is new" and "this was deleted elsewhere".

1.11.0 2026-09-16

Added

• Reminders to record an odometer reading (#33). Mileage is worked out between readings, so a gap between them leaves those months blank — and they can't be filled in afterwards. The app now notices when a car's last reading is older than an interval you choose (Settings → Odometer Readings; every 3 months by default), badges the car, lists the overdue ones, and sends a notification that opens straight into that car's entry sheet. Counted from each car's last reading, not a fixed date.
  • This is deliberately about readings, not activity: the existing "no recent entry" badge was satisfied by a cost-only entry, so a car with monthly insurance and no reading for a year looked fine.
• A real first-run screen (#11). It used to open on "Where Should Your Data Live?" and two buttons — asking you to decide before saying what the app does or why a spreadsheet is involved. Now it says what it's for, what each storage option means for you, and that the AI features are optional.

Fixed

• Saving a report on the Mac works again (#32). The Mac was getting the iPhone share sheet, which has no "Save to Files" — a menu with no way to save the report at all. Same root cause put the camera button and document scanner back on the Mac, where they can't work.
• An edit no longer vanishes for 30 seconds (#41). If a refresh started while an earlier change was still uploading, the change could disappear from the screen until the next refresh.

1.10.1 2026-09-16

Fixed

• Moving your data to Google no longer loses your car values. 1.10.0's own fix for cross-client edits accidentally made the migration write every car with a blank "Your value" and no estimate history — into a sheet it had just cleared, with the on-device copy deleted straight after. Unrecoverable. If you ran a move to Google on 1.10.0, check your values.
• "Update Estimates" no longer wipes a value you set on the web. The AI refresh was writing the price column as well as the estimates, and it only runs on cars it thinks have no price — which is exactly when another device has just set one.
• Plug-in hybrids get their MPG back. 1.10.0 started treating a charge as a break in the petrol chain (and a fill as a break in the charging chain), so a car that does both reported far worse economy than it gets.
• A queued offline car edit no longer restores its own stale value over a newer one when it replays.
• A document deleted on another device no longer reappears when a queued rename replays.
• Renaming a file from the rename sheet no longer strips a dot-suffix that isn't really an extension — the sheet had its own copy of the old rule.
• The expenses drill-down now ends where its bar does, like mileage already did.
• An AI estimate that fails offline no longer promises to sync later.
• On-device mode no longer reports itself "offline" when a read fails; there is nothing to be offline from.

1.10.0 2026-09-16

Fixed

• Editing a car on the phone no longer wipes a value you set on the web. Every save wrote the whole row from the phone's copy, so renaming or retiring a car blanked "Your value" if the web had set it since the phone last read — the garage total silently reverting to the AI estimate. A save now writes only what it changes. Same for renaming a document versus marking it as from a previous owner: those two used to undo each other, with no conflict check at all on that sheet.
• "Missed a fill-up before this" works on a cost-only entry. Gallons are optional, and an entry without them was dropped from the economy chain before the flag was ever read — so the next fill was measured straight across the unlogged fuel and could read double the real MPG. A fuel stop with no amount now breaks the chain whether or not you tick the box.
• A cost dated next month no longer inflates a car's bar. Pre-pay a registration and the per-car bar counted it while the drill-down you get by tapping that bar stopped at this month, so the two didn't add up.
• On-device mode offers Try Again when a read fails, instead of an empty garage inviting you to add your first car on top of data that is still there.
• A failed first Google sign-in no longer says your access "expired or was revoked". It never existed, and Settings just repeated the same failure; the message now says sign-in failed and why.
• "Will sync as soon as you're back online" is only promised where it's true. Reference photos, AI estimates, document scans, opening a file and data moves aren't queued — they need doing again, and now say so.
• Renaming a file whose name contains a dot but no real extension ("Invoice no.5") no longer invents one, giving you "Registration.5".
• A deleted document no longer flickers back into the list when a refresh lands inside its 8-second Undo window.

1.9.1 2026-09-15

Fixed

• Deleting something no longer loses it if you move your data. A file inside its 8-second Undo window was hidden from the app but not yet deleted — and starting a move to Google or to this device in that moment copied everything except that file, then destroyed the original. The record and the file were both gone, with Undo still on screen. Cancelling a pending delete now puts the row back first, and the Undo banner goes away with it.
• A corrupt local file no longer erases your garage. In on-device mode, a store file that couldn't be read was quietly replaced with an empty one on the next launch — no error, just an empty garage and nothing to recover from. The file is now left alone and the app tells you, so a backup can still restore it.
• A move to Google can't destroy your spreadsheet half-way through. The destination was cleared before anything was uploaded, so a dropped connection during the upload left it permanently empty. Clearing now happens after the files are safely across.
• Moving data from a store that failed to open is no longer offered. It would have cleared the destination and deleted the local copy while holding nothing to move.
• A revoked Google sign-in no longer discards queued changes. Edits made after access was revoked were treated as ordinary failures and dropped after five retries, despite being the exact case the app promises to hold onto. The sign-in badge now offers to reconnect instead of silently doing nothing, and the message says what to do rather than "You're not signed in to Google."
• An error arriving while Undo was on screen used to replace it, removing the only way to stop a delete that still went ahead. It now waits its turn.
• A missing file on this device is no longer reported as missing from Drive.
• A failed move no longer hides a "reconnect" instruction behind "couldn't refresh".

Changed

• The tests guarding error messages now check the behaviour a release build has. They were passing in Debug for a reason unrelated to the code, so they could not have caught the bug they were written for — verified by deleting the code and watching them stay green.

1.9.0 2026-09-14

Added

• The first screen now asks where your data should live. The Dashboard and Reports tabs used to say "Not Connected — Connect in Settings" with nothing to tap, and Dashboard is the tab the app opens on. Both now offer the same two buttons the Garage tab always had.
• "Try Again" when a load fails. A first read that timed out used to show "Not Connected", which told a signed-in user to go and reconnect — while the banner underneath said it would sync itself. Failed loads are now their own state with a retry that re-opens whichever store you chose.
• Undo for deleting a report or document. Delete lives in a long-press menu right under "Open in Drive", and one mis-tap used to destroy a scanned title or a buyer dossier for good. The row disappears at once and the delete only commits after an 8-second Undo window.
• Share on saved reports. The share sheet used to appear exactly once, right after generating — so emailing Thursday the dossier you built on Sunday meant regenerating it. Share is now in the row's menu, including in local-only mode.
• Charts say when they're hiding a car. A car with no activity in the range, or fewer than two fill-ups, simply vanished — indistinguishable from one whose entries hadn't synced. Each chart now names how many are missing and why.
• Errors keep their own wording. An independent review found the new error mapper was swallowing the app's own messages: a blocked migration, a denied Google permission, or a mistyped AI address all came out as "Something went went wrong — try again." The mistyped-address case was the worst, since "try again" could never work. Those messages now survive, with tests so they stay that way.
• A revoked Google session can reconnect again. If access was revoked part-way through a load, the app concluded the session was fine and offered a retry that could never succeed — with the reconnect button hidden, so Disconnect was the only way out. It now recognises that case.
• Undo covers album photos too, not just documents and reports.

Changed

• The dashboard keeps its controls while loading. A cold launch replaced the whole screen with one centred spinner; the metric and range pickers now stay live so you can set up the view you want while the read is in flight, and the text says what it's fetching instead of "Syncing", which is also what the background-refresh badge says.
• A visible way out of a single-car chart. Getting back used to mean reading a caption and finding that car in a ten-item legend — and when any bar was an estimate, the caption said something else entirely and there was no instruction at all. There's now an "All cars" button beside the chart title.
• "Spent" says "(all time)". It sums every entry ever but sat above the 1M/3M/6M range pills and a "last 6 months" caption, so it read as six-month spend and didn't change when you tapped 1M.
• The garage total says how many cars it covers — "Estimated total (8 of 9 cars)" — and cars without an estimate say "No estimate" on their own row, instead of the shortfall being sentence three of a grey footer with no way to tell which car.
• Error messages name the next step. A Google failure used to put its raw API text in the banner ("Google API error 403: {300 characters of JSON}"). Rate limits, outages, expired access and missing sheets now each say what to do; the raw text is kept for debug builds.
• Report names truncate in the middle. Every name starts with the same date, so cutting the end hid the only part that identified the file.

Fixed

• Charts and the "Cars" count disagreed. The tile counted active cars while every chart drew retired ones too — 9 against 10 bars — so retired mileage quietly inflated fleet comparisons.
• The floating add button permanently covered the last row of the Garage list; the list now has the bottom clearance the Dashboard already had.
• The error banner covered the navigation title it appeared over.
• The Undo button's tappable area was the word "Undo" rather than the button drawn around it, well under the minimum target size — on the one control in the app with a countdown attached.
• A pending delete could outlive a sign-out or a data move and then try to delete a file in the wrong place.
• A rotated phone had no way out of a single-car chart, and a car retired while you were looking at it became unclearable.
• An unrelated edit during an undo window could leave the deleted row hidden until the next successful sync.
• Retired cars were labelled "No estimate" forever, contradicting the count in the footer above them.
• Tapping a document twice while it was still downloading cleared the preview.
• Local-only mode showed a healthy "on this device" in Settings even when the store had failed to open, with no way to retry.

1.8.2 2026-09-14

Fixed

• Chart text on the Mac is actually larger now. 1.8.1 shipped bigger Mac chart sizes that never applied, because the Mac test was #if targetEnvironment(macCatalyst) — a compile-time condition that is false in the iOS binary, and TestFlight hands the iOS binary to an Apple Silicon Mac ("iPad app on Mac"). The check is now ProcessInfo.isMacCatalystApp, which is true for a Mac Catalyst app and for the iOS app running on macOS, so it fires whichever build is installed. Sizes went up again as well, and the per-car bar chart's value axis was picking up the default size instead of the Mac one.

1.8.1 2026-09-14

Fixed

• Chart text is legible on the Mac. Axis labels, the numbers at the end of each bar, legends and the captions under each chart were all rendering about a quarter smaller on macOS than on iPhone — Mac Catalyst draws the iPad interface at 0.77 scale, which body text absorbs and an 11-point axis label does not, particularly across a window three times the width of a phone. Chart type now has explicitly larger sizes on Mac, chosen to land at the same apparent size as on iPhone. The iPhone and iPad are untouched, and so are the PDF reports — they share those chart views, and a report should look the same whichever device made it.

1.8.0 2026-09-14

Changed

• The expenses graph ranks your cars, like mileage does. It was a stacked monthly chart, so working out which car actually costs the most meant comparing the heights of coloured segments by eye. Expenses is now one bar per car totalled over whatever range you've picked — the ranking is the chart — and tapping a car's bar shows that car's spending month by month. The fleet-wide monthly view it replaces is still there per car, one tap in.

Added

• The app keeps itself up to date while you're looking at it. It now re-reads your data every 30 seconds whenever it's the app in front, so a Mac window left open beside you picks up what you logged on the phone without being touched. Foregrounding still triggers a read as well, and nothing polls in the background or in on-device mode, where there's nothing to poll.

Fixed

• A car you'd tapped into can always be untapped. On a chart tab with no data in the selected range — or when the car had been deleted on another device, or simply had too few fill-ups to chart — every bar dimmed with no way to clear the selection. Every tab that dims for a selection now offers a way back. (The Total chart never dims, because it isn't per-car.)

1.7.1 2026-09-14

Changed

• Report filenames all start with the date now. The four report types each built their own name and had drifted into three different shapes — the garage report, the car report and the vehicle-history packet put the date at the end, while the fleet report put it at the front. Every one is now YYYY-MM-DD — what it is — which car, so a Reports folder sorts chronologically wherever you look at it. Reports you already generated keep the names they were saved with.

1.7.0 2026-09-14

Changed

• Chart ranges are 1M / 3M / 6M / 1Y / All, and every one is a tap. The range used to be a single pill showing where you already were, which you tapped to cycle forward — fine with four ranges, tedious with five. All five now sit under the chart tabs with the current one filled in, so any window is one tap away and you can see which is active without touching anything. 1M and 3M are new; 2Y is gone, since All covers it. Swiping up and down over the chart still steps through them.

Fixed

• A second device now notices what the first one did. Reports generated on the iPhone didn't appear on the Mac until Garage Buddy was quit and relaunched. Two things caused it: the Reports tab had no pull-to-refresh (the Dashboard and Garage have had one all along), and coming back to the app only re-read your data if the last sync had actually failed — an app sitting there connected never asked for anything new. Returning to the app now re-reads if what's on screen is more than a minute old, and the Reports tab can be pulled down like the others.

1.6.0 2026-09-14

Added

• A Reports tab, and reports that are kept. Reporting used to be four buttons hidden in the toolbars of three different screens, and what they produced existed only in the share sheet — dismiss it and the report was gone. There's now a fourth item in the dock where all four are generated: the fleet report, the whole-garage PDF, and — with a car picker — a single car's report and its vehicle-history packet. The car page and the garage keep their own screens uncluttered; their export buttons have moved here.
• Every report is filed and listed. Generating one saves it to a Reports folder in your Google Drive, alongside the per-car folders, and it appears under "Saved reports" in the tab — tap to read it again, or long-press to open it in Drive, rename it, or delete it. Reports save the same way attachments do, so generating one works offline and uploads when you're back; on-device mode keeps them on the device instead. The fleet report, which was previously only ever a screenful of text, is now saved as a PDF like the rest — writing it files it automatically, and "Save the Numbers as a Report" keeps the figures on their own whether or not you have an AI key.

Fixed

• Reading a car document is sharper and cheaper. "Extract Details" on a title, registration or insurance card rendered the PDF at about 72dpi — legible for a heading, marginal for the VIN underneath it — and sent every page of the file, however long. It now renders at roughly 150dpi and stops after the first few pages, which is where a document says what it is. The same rendering the receipt scan has used since 1.5.0.

Changed

• The mileage graph now compares cars, and a new Total graph shows the fleet. The Mileage tab was a stacked monthly chart that answered two questions at once and neither cleanly: which cars you actually drive meant estimating the size of coloured segments by eye, and how much you were driving overall was hidden by every bar being split up. Mileage is now one bar per car, summed over whatever range you've swiped to — so the ranking is the chart — and tapping a car's bar still shows that car month by month, now matching the range you picked. A new Total tab next to it shows every car's miles combined, one bar a month.
• The fleet report says what the money was actually spent on. It treated a car's spending as one number, so a set of tires filed under Maintenance came back as "$900 in maintenance" — which reads as a car that keeps needing work rather than one purchase. The report now breaks the period's spending down by category, with the number of entries behind each total, and a category that is really a single item says so. The written summary is told the same thing and is told not to describe a one-off as ongoing servicing.

1.5.1 2026-09-07

Changed

• The MPG chart makes room for a full garage. With eight cars on it, the bars, the car names, the numbers, and the gridlines were all crushed into one 260-point band and the colour legend wrapped onto a second line repeating names the chart already showed. The chart now grows with the garage — each car gets a proper row and the dashboard scrolls — the legend is gone from this view, and the horizontal gridlines that ran between rows went with it. Tap a bar now, rather than a legend entry, to drill into that car's fill-ups; the per-fill view keeps its legend for switching cars and going back. The number on the longest bar no longer runs off the edge.

1.5.0 2026-09-05

Added

• What your garage is worth. The Garage screen now leads with an estimated total, how it has moved since the last estimate, and a per-car figure on each row; a car's own page shows its value, the change, and how it compares to what you paid. Values come from the AI you've already configured — one small text-only question per car, from its year, make, model and mileage — so this appears only if you've set up an AI key, and every figure is labelled as an estimate with the date behind it. They're cached and topped up at most once a launch, and only when a car has never been valued or its estimate has passed 30 days, so a ten-car garage costs roughly ten small calls a month; "Update Estimates" re-runs the lot on demand. A generic estimate is worst exactly where cars are most interesting, so Your value in a car's Edit screen overrides it everywhere, including the garage total — set it for modified, rare, or project cars and that car is never asked about again.
• Documents from before you owned the car. A car's paperwork often arrives with it — the previous owner's service invoices, an inspection report, the bill of sale. Long-press any document on a car's page and mark it "From a Previous Owner": it moves into its own Previous Owner section, wears a badge, and is described as inherited history everywhere it appears. It counts as a record, never as your mileage — these are car documents, which carry no odometer reading, so nothing about them can reach your mileage history, averages, projections, or service intervals. They travel with the car: listed and marked in the car report, and — unlike your title, registration, and insurance, which stay private — included in the vehicle-history packet you hand a buyer, because a previous owner's service record is exactly what that packet is for.

Fixed

• Two fill-ups on the same day drew one bar at their combined MPG. The per-fill economy chart bins its bars by day, and same-day bars were stacked — the default — so two 30 MPG fills rendered as a single 60 MPG bar and dragged the y-axis up with them. Each bar is now drawn from zero, one per fill, as the caption under the chart always claimed. Only the chart was affected: the stored entries, the car's average MPG and the moving-average line were right the whole time.
• A PDF receipt now gets read, like a photographed one. Adding a receipt with "Choose PDF" attached the file and stopped there — no scan, no filled-in fields — while the same receipt photographed or scanned with the camera came back with its vendor, date, total, and a summary already in place. The PDF path now runs the same extraction: its pages are rendered and read, and the entry is pre-filled for you to check. Needs an AI key, like every other scan; without one the file is simply attached as before.
• PDF pages are rendered at a readable size before being read. They were rasterised at their natural point size — about 72dpi, which is legible for a heading and marginal for the line items under it. Receipts and documents are now rendered at roughly twice that before going to the AI, which also helps the "Extract Details" action on a document you added earlier.

Removed

• The fuel-price graph is gone. The "Fuel $" tab charted what you paid per gallon at each fill. It mostly drew the pump price at the stations you happen to use — a picture of the fuel market, not of your car — so it took up a tab without telling you anything you could act on. Mileage, expenses, and fuel economy are unchanged, and nothing about your fills was deleted: the cost and gallons on every entry are still there and still feed economy and cost-per-mile. A more useful money-per-distance view can take the slot later.

1.4.1 2026-08-29

Fixed

• A seeded run could resync the real account over the sample fleet. -seedSampleData populates a demo garage and start() returns before any auth or network — but scene activation calls resumeSyncIfNeeded() straight afterwards, which reconnected and pulled the live Google Sheet back over the seeded data, usually a second or two after launch. Anyone capturing screenshots got real cars while believing the demo fleet was on screen. That is how twelve real cars, their photos and real spend reached the 1.3.0 Mac App Store listing. A seeded run now refuses to sync. DEBUG only.

Changed

• Mac App Store screenshots now come from the sample fleet. Replaces the three shots on the macOS listing, which were captured from a real garage: cars by name, year, model and exact odometer, the owner's own photos of them (driveways, a house, a street), total spend, and a dated activity log. Screenshots on a READY_FOR_SALE version can only be replaced by submitting a new version, so this release exists to carry the clean ones.
• New tools/capture-mac-screenshots.sh. Builds, launches the seeded app three times and captures each tab at exactly 2560x1600, so the store assets are reproducible instead of hand-grabbed. Backed by a DEBUG-only -screenshotFrame x,y,w,h launch argument that pins the window to an exact rect — Catalyst renders at 0.77 scale, so the numbers in the script are pre-calibrated to land on 1280x800 points.

1.4.0 2026-08-23

Added

• "Missed a fill-up before this" on gas and charging entries. When a tank gets filled without being logged — someone else fills it, a jerry can, a receipt that never made it home — the next fill you log looks like it covered two tanks' worth of miles on one tank of fuel, and its MPG comes out roughly double. Turn the switch on when logging that next fill: its MPG is left out of the per-fill chart and the car's average, and the fill after it measures from there, so one unlogged stop no longer bends the trend line. The entry is otherwise a normal entry — its odometer, cost, and gallons still count everywhere else — and it's marked "after a missed fill" in history lists so the gap in the chart has a visible reason.

1.3.0 2026-08-07

Removed

• The Mac no longer offers camera capture. "Take Photo" and "Scan Document" are gone from the Mac build. Every capture flow here means walking up to a car to photograph an odometer, a pump, or a receipt, and a Mac's camera is fixed to the screen facing the user — the buttons had no plausible use even where they worked. On the Mac they did nothing at all: a sandboxed app is denied the camera silently unless it claims the camera entitlement, so no permission prompt ever appeared. That is the App Review guideline 2.1 rejection for 1.1.0. Macs add photos and documents with "Choose Photo" and "Choose PDF", or scan on the iPhone and let it sync. iPhone and iPad are unchanged.

Fixed

• Choosing a photo from the library left you with no obvious way out. On the Mac, the photo picker offers a checkmark to confirm but no Cancel, so changing your mind meant guessing that the Escape key would work. The Mac picker now has a Cancel button. iPhone and iPad already had one.
• Library picking no longer uses a deprecated picker. It ran through UIImagePickerController, which Apple deprecated for library access in favour of the modern photo picker and which behaves poorly on the Mac, and it was presented as a full-screen cover — which fills the whole Mac window and, unlike on iPhone, can't be swiped away. Every library pick now uses the modern picker in an ordinary sheet.
• A refused camera now explains itself. On iPhone and iPad, "Take Photo" asks for permission before opening the camera and, if it's refused, says where to turn it back on instead of leaving a button that does nothing. The odometer scan launched from the widget or a shortcut falls back to the photo-source dialog, so it offers the library rather than dead-ending.

1.2.3 2026-08-05

Fixed

• Documents are named for when they were issued, not when they expire. 1.2.2 led a registration's filename with its expiration, filing a registration issued this year under next year. The document scan now reads the issue/effective date as well — it previously extracted only the expiration, which is why the name reached for the wrong one — and that is what the filename leads with: "2026-03-14 — Registration.pdf". A document showing only an expiration gets no date rather than a misleading one. The expiration is still read and still drives the renewal reminder; it just doesn't name the file.

1.2.2 2026-08-05

Changed

• Document names lead with the document's own date, in YYYY-MM-DD. A receipt is now "2026-07-16 — Les Schwab.pdf", so documents sort chronologically in the app, in Drive, and in Files. The date is read off the document, never today's; a document with no date of its own gets no date rather than a filing date, which would say when you scanned it instead of what it is.

1.2.1 2026-08-05

Fixed

• "Suggest a Name" reported readable receipts as unreadable. The document read only knows vehicle paperwork — title, registration, insurance — so a receipt came back classified as "other", and the app turned "I have no name for this kind of document" into "Couldn't read that document", sending you looking for a problem that wasn't there. Receipts are now read as receipts and named for the vendor and date ("Les Schwab — 2026-07-16.pdf"), and the two failures are told apart: one message for a file that wouldn't open, a different one for a document that was read but couldn't be named.

1.2.0 2026-08-05

Added

• Scanned documents name themselves. With an AI key configured, a document you photograph or scan is read before it's saved and filed under a name worth reading — "Registration — expires 2027-03.pdf", "Insurance — State Farm.jpg" — instead of "Document 2026-08-05.pdf". The name comes from the structured fields the app already extracts, not from asking a model to invent a filename. Characters a filename can't hold (slashes, colons, newlines and the rest) are replaced, names are length-capped on a word boundary, and anything unusable falls back to the old dated name. No key, no signal, or an unrecognised document all fall back silently — the document still saves. Files you import keep the name you already gave them.
• Rename a document. Long-press any car document → Rename. The extension is preserved for you, so a file can't stop opening as a PDF because the name was cleared. With AI configured, "Suggest a Name" reads the document and fills the field for you to accept or edit — it never applies a name behind your back, and it says so rather than replacing a good name with a generic one when it can't tell what the document is. Renaming also renames the file in your Google Drive, so the two don't drift apart.
• Full vehicle history — the packet you hand a buyer. A car page now has two export buttons. The existing share button still produces the quick report; the new one builds a complete history document: a cover page, an AI-written history of the car (how long you've had it, how it's been used, what's been repaired and when), charts for mileage, spending, where the money went, and fuel economy per fill, then the service and repair record with your notes in full, the complete log, a page or two of photo thumbnails, and the scanned receipts themselves.
  • It deliberately withholds what a buyer shouldn't get. No purchase price, sale price, or profit anywhere in it. No title, registration, or insurance documents — those carry VIN provenance, policy numbers, and your address — and no receipts filed under Insurance or Registration. Those entries still appear as lines in the log; only their scanned images are held back. Nothing is removed from the app or the quick report.
  • It degrades instead of failing. No AI key or no signal means the history page is simply left out, and any attachment that can't be downloaded is counted in the document ("2 attachments couldn't be downloaded") rather than quietly missing. Photos beyond the two-page cap are reported the same way.
  • Receipts are downscaled before embedding, so a packet with dozens of them stays a sane file size. Multi-page PDF receipts are included in full, each page captioned "page 2 of 3" — a shop invoice often runs its line items and totals onto later pages.
  • The progress panel says what it's actually doing instead of one unchanging line: which step is running, what it's working on right now (the model being asked, or the file being fetched and how far through), and a per-step seconds counter so a slow AI call is visibly alive rather than apparently hung. Past eight seconds it also notes that the writing step usually takes 10–30 seconds.

1.1.0 2026-08-01

Added

• Garage Buddy on the Mac. The app now runs natively on macOS (Mac Catalyst). Sign in with the same Google account and it reads and writes the same spreadsheet as your iPhone — edit on either, and the change shows up on the other. On-device mode stays per-device, since there's no shared storage to sync.
• iPad support. Required for the Mac build, and the layout adapts.

Fixed

• PDF reports couldn't be saved on the Mac. Exporting a report opened the macOS Share menu, which offers share destinations only — AirDrop, Mail, Messages — with no way to save the file. "Save to Files" is an iOS-only share action; on macOS saving belongs in a save panel. The Mac build now opens a proper save panel, and iPhone/iPad keep the share sheet (where Save to Files already appears alongside AirDrop and Mail). This also clears the duplicate "Copy" entry the Mac menu was showing.
• Buttons were nearly invisible in dark mode. The accent colour had no dark-appearance variant, so blue-on-dark text sat at a 1.21:1 contrast ratio against a 4.5:1 accessibility minimum — worst on Settings, where "Connect Google Sheets" and "Keep Everything on This Device" were barely legible. Now 5.11:1. This affected iPhone dark mode too, not just the Mac.
• The app called itself "CarLog" on the Mac — in the menu bar, in Finder, and in the macOS "…wants to use accounts.google.com to sign in" prompt. It now says Garage Buddy everywhere.

1.0.0 2026-07-24

Changed

• First public release. No functional change from 0.38.4 — this version exists so the build matches the 1.0 record in App Store Connect. Every feature below shipped and was field-tested through the 0.x TestFlight series: local-first or Google Sheets storage with two-way migration, AI/on-device odometer scanning, per-fill MPG and MPGe, reminders and service intervals, photo albums and document scans, PDF reports, and home-screen widgets.