[Due for payment 2025-02-13] [$250] Android - Track expense - Error when creating track scan expense from Quick action

[IuliiaHerets]

If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!

---

Version Number: 9.0.85-0
Reproducible in staging?: Yes
Reproducible in production?: Yes
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: Yes, reproducible on both
If this was caught during regression testing, add the test name, ID and link from TestRail: Exp
Email or phone of affected tester (no customers): Samsung Galaxy Z Fold 4 / Android 14
Issue reported by: Applause Internal Team
Device used: [email protected]
App Component: Money Requests

Action Performed:

1. Launch ND or hybrid app.
2. Go to self DM.
3. Create a track scan expense.
4. Go back to LHN.
5. Open FAB.
6. Tap Track receipt under Quick action.
7. Upload a receipt and submit.
8. Go back to LHN.

Expected Result:

The second track scan expense should remain in self DM when created from Quick action.

Actual Result:

The second track scan expense disappeas from self DM after it is created from Quick action.
It appears as an error report with RBR in LHN.

Workaround:

Unknown

Platforms:

• Android: Standalone
• Android: HybridApp
• Android: mWeb Chrome
• iOS: Standalone
• iOS: HybridApp
• iOS: mWeb Safari
• MacOS: Chrome / Safari
• MacOS: Desktop

Screenshots/Videos

Bug6714224_1736884791029.Screen_Recording_20250115_035537_Media_picker.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~021882503761567985375
• Upwork Job ID: 1882503761567985375
• Last Price Increase: 2025-01-23

Issue Owner

Current Issue Owner: @VictoriaExpensify

[melvin-bot]

Triggered auto assignment to @VictoriaExpensify (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.

[jacobkim9881]

#54628

On android, receipt image isn't instanceof Blob so the receipt is changed into undefined

App/src/libs/actions/IOU.ts

Line 4330 in 7b9e55e

receipt: trackedReceipt instanceof Blob ? trackedReceipt : undefined,

@CyberAndrii could you please to check?

[CyberAndrii]

Thanks @jacobkim9881. We will need another PR for this @Pujan92.

Why does it work when tracking via FAB but not QAB 😕

[jacobkim9881]

@CyberAndrii Sad to notice this 😕 Good for you to fix this tho

[melvin-bot]

Triggered auto assignment to @deetergp, see https://stackoverflow.com/c/expensify/questions/7972 for more details.

[melvin-bot]

Job added to Upwork: https://www.upwork.com/jobs/~021882503761567985375

[melvin-bot]

Triggered auto assignment to Contributor-plus team member for initial proposal review - @getusha (External)

[jacobkim9881]

I think this will be solved as #55321 is merged.

[melvin-bot]

@deetergp, @VictoriaExpensify, @getusha Whoops! This issue is 2 days overdue. Let's get this updated quick!

[melvin-bot]

@deetergp, @VictoriaExpensify, @getusha 6 days overdue. This is scarier than being forced to listen to Vogon poetry!

[deetergp]

Looks like this was merged and deployed to staging. I have asked for a retest in our QA channel here https://expensify.slack.com/archives/C9YU7BX5M/p1738687602185819

[m-natarajan]

Issue fixed

1738661568715.55321_Android.mp4

[deetergp]

Thank you @m-natarajan. Closing this one out.

[melvin-bot]

Reviewing label has been removed, please complete the "BugZero Checklist".

[melvin-bot]

The solution for this issue has been 🚀 deployed to production 🚀 in version 9.0.94-25 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:

• Improve receipt file detection #55321

If no regressions arise, payment will be issued on 2025-02-13. 🎊

For reference, here are some details about the assignees on this issue:

• @getusha requires payment through NewDot Manual Requests

[melvin-bot]

@getusha @VictoriaExpensify @getusha The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]