[Tracking] Android/iOS - Issues scanning a receipt and backgrounding the app

[mountiny]

If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!

---

Version Number:
Reproducible in staging?:
Reproducible in production?:
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: @heyjennahay @mjasikowski
Slack conversation (hyperlinked to channel name): https://expensify.slack.com/archives/C049HHMV9SM/p1755616201447209

Action Performed:

Break down in numbered steps

1. I scan the receipt
2. The expense says "scanning..."
3. If I turn off the app now and reopen it, the expense still says "scanning" and I'm unable to edit it (always errors)
4. If I launch NewDot on another platform this expense is not there

---

1. Open NewDot mobile app on Pixel 6 (Android)
2. Take a photo of receipt
3. Put phone away
4. Come back to mobile and view the expense
5. See that there is a photo of the receipt + the date, amount and merchant have been SmartScanned + expense has been auto categorised
6. Expense has error stating There was an error uploading your receipt. Please try again or save the receipt to upload it later
7. Click X on error
8. Modal appears stating Heads up! Dismissing this error will remove your uploaded receipt entirely. Are you sure?
9. Click Dismiss
10. See that the expense has been removed from the report
11. Go back to the Inbox and click into the report again
12. Scroll to the bottom
13. Initially the expense is not there
14. A moment later it appears without the upload error

Expected Result:

Describe what you think should've happened

The receipt is uploaded and scanned even if the app is backgrounded

Actual Result:

Describe what actually happened

When the app is backgrounded the upload seems to fail, sometimes even silently

Workaround:

Can the user still use Expensify without this being fixed? Have you informed them of the workaround?

Platforms:

Select the officially supported platforms where the issue was reproduced:

• Android: App
• Android: mWeb Chrome
• iOS: App
• iOS: mWeb Safari
• iOS: mWeb Chrome
• Windows: Chrome
• MacOS: Chrome / Safari
• MacOS: Desktop

Platforms Tested:

On which of our officially supported platforms was this issue tested:

• Android: App
• Android: mWeb Chrome
• iOS: App
• iOS: mWeb Safari
• iOS: mWeb Chrome
• Windows: Chrome
• MacOS: Chrome / Safari
• MacOS: Desktop

Screenshots/Videos

Add any screenshot/video evidence

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~021986093082786378473
• Upwork Job ID: 1986093082786378473
• Last Price Increase: 2025-11-12

Issue Owner

Current Issue Owner: @jliexpensify

[melvin-bot]

Triggered auto assignment to @jliexpensify (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.

[MelvinBot]

This has been labelled "Needs Reproduction". Follow the steps here: https://stackoverflowteams.com/c/expensify/questions/16989

[jliexpensify]

Posted my thoughts here - https://expensify.slack.com/archives/C049HHMV9SM/p1756852748540409?thread_ts=1755616201.447209&cid=C049HHMV9SM

Experienced last week

[mjasikowski]

trim.9BE20D0B-2CAA-499A-9050-ED59683E7EDA.MOV

[gedu]

Hi I'm Edu from Callstack, I can take a look at this