Receipt scanning fails with "Couldn't read that image"
Fix in progressWhat happens: starting a receipt scan (＋ → Expense → Scan a receipt) fails with a generic “Couldn’t read that image” message, from both the camera and photo import.
What we know: the failure is in the on-device text-recognition step. A diagnostic build adds the specific error type to the message in parentheses — for example “Couldn’t read that image (TYPE)” — which is safe to share and is exactly what we need in reports.
What to do in the meantime:
- Use manual entry for the transaction — it always works and loses nothing except the scan convenience.
- If you are on a build that shows the error type, please report it and include the TYPE in parentheses, whether you used the camera or photo import, and your device model. Never send the receipt image itself if it shows card numbers or personal details.
Status: fix in progress; a diagnostic build is rolling out through TestFlight to pin down the exact failure.