fixin

Results that say the same thing everywhere How sure the app is now reads the same on every screen. A result that says "Possible match" in your History says "Possible match" when you open it — before, the two screens were measuring different things and could disagree about the same diagnosis. The threshold behind that wording was also wrong for what it was applied to, which pushed almost everything into the red "Low match" band — and made a more specific answer score worse than a vague one. It is rebuilt, so the wording now tracks what the app actually knows. The heading is the category. The largest text on a result is now the broad category, which is the level the app is most often right about, with the specific fault underneath as the qualifier it is. Where naming a specific fault would be a guess, the app stops at the category and tells you so, rather than showing something precise with a confident-looking number beside it. Parts and tools that match the actual repair The supplies list came from a keyword table that only knew about cars, so a boat teak refinish was offered a socket set and a "replacement part". It now comes from the same repair guide you are reading — all 2,262 of them — so the list matches the job. Your History opens the whole diagnosis. Tapping a saved diagnosis used to show a cut-down summary card. It now opens the full result, with repair instructions, parts and tools, and support options, the same page you saw when you ran it. Older saved diagnoses come back too, with whatever detail was stored for them. Choose your engine Every plan can now pick which on-device engine runs a diagnosis, in Settings. New engines can arrive without waiting for an App Store update, and the app quietly checks for one in the background. Scan without installing The App Clip is a working diagnosis now: open it from a code or a link, point the camera at the problem, and get the category and how strong the match is, then carry it into the app. No account, nothing uploaded — it runs on the device. Also in this release With a paired OBD-II reader, Settings can stream live readings from the vehicle's computer, showing only the sensors your vehicle actually reports. Fixed Connecting to an OBD-II reader that was out of range could hang the app. Vehicle identification numbers could come back garbled, a trouble code could be read as a different one, and "no trouble codes found" could really mean the app never reached the vehicle at all. A home diagnosis could show a label like "Av". Buttons and controls that drew in the system tint — the camera's Use Photo bar, share and PDF views, alert buttons — were nearly invisible against the app's dark background.