You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[$50] Scan - Not here page opens when opening Amount field after reset and restart app #59989
Version Number: 9.1.26-0 Reproducible in staging?: Yes Reproducible in production?: No If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: No, reproducible on hybrid only 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):jsjsdmodsoi019@gmail.com Issue reported by: Applause Internal Team Device used: Samsung Galaxy Z Fold 4 / Android 14 App Component: Money Requests
Action Performed:
Go to staging.new.expensify.com
Log in with a new Gmail account.
Create a workspace.
Go to workspace chat.
Submit a scan expense with an invalid receipt that will fail the scanning.
Go to the transaction thread
After the scanning fails, go to Settings > Troubleshoot.
Click Clear cache and restart > Reset and restart.
Go to Inbox.
Click Amount field quickly (important).
Note that not here page opens.
Close the RHP.
Note that there is a report "Receipt missing details" with RBR in LHN and it is grayed out.
Click on that report.
Note that the report has grayed out header and missing composer. It disappears from LHN after opening it.
Expected Result:
In Step 11, when opening Amount page, app will open amount input page.
In Step 15, the report named "Receipt missing details" will not gray out.
Actual Result:
In Step 11, when opening Amount page, app opens not here page.
In Step 15, "Receipt missing details" report header is grayed out and the composer is missing.
👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open `StagingDeployCash` deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:
Identify the pull request that introduced this issue and revert it.
P.S. Is everyone reading this sure this is really a near-term priority? Be brave: if you disagree, go ahead and close it out. If someone disagrees, they'll reopen it, and if they don't: one less thing to do!
Activity
melvin-bot commentedon Apr 10, 2025
Triggered auto assignment to @zanyrenney (
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.melvin-bot commentedon Apr 10, 2025
Triggered auto assignment to @mountiny (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.melvin-bot commentedon Apr 10, 2025
💬 A slack conversation has been started in #expensify-open-source
github-actions commentedon Apr 10, 2025
👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open `StagingDeployCash` deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:
26 remaining items
melvin-bot commentedon May 22, 2025
This issue has not been updated in over 15 days. @mountiny, @zanyrenney, @dukenv0307 eroding to Monthly issue.
P.S. Is everyone reading this sure this is really a near-term priority? Be brave: if you disagree, go ahead and close it out. If someone disagrees, they'll reopen it, and if they don't: one less thing to do!
melvin-bot commentedon Jul 18, 2025
@mountiny, @zanyrenney, @dukenv0307, this Monthly task hasn't been acted upon in 6 weeks; closing.
If you disagree, feel encouraged to reopen it -- but pick your least important issue to close instead.
izarutskaya commentedon Jul 22, 2025
Not repro on mWeb/Chrome
0-02-01-bd72b26ae3914a10ede806d343e447c9e93a0308d12422d18003afd540f17f92_f71d44307339a668.1.mp4
mountiny commentedon Jul 22, 2025
I guess we can close now