Skip to content

[$50] Scan - Not here page opens when opening Amount field after reset and restart app #59989

Closed

Description

@mitarachim

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: 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:

  1. Go to staging.new.expensify.com
  2. Log in with a new Gmail account.
  3. Create a workspace.
  4. Go to workspace chat.
  5. Submit a scan expense with an invalid receipt that will fail the scanning.
  6. Go to the transaction thread
  7. After the scanning fails, go to Settings > Troubleshoot.
  8. Click Clear cache and restart > Reset and restart.
  9. Go to Inbox.
  10. Click Amount field quickly (important).
  11. Note that not here page opens.
  12. Close the RHP.
  13. Note that there is a report "Receipt missing details" with RBR in LHN and it is grayed out.
  14. Click on that report.
  15. 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.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

20250410_140646.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~021910295578085557157
  • Upwork Job ID: 1910295578085557157
  • Last Price Increase: 2025-04-10
Issue OwnerCurrent Issue Owner: @dukenv0307

Activity

  1. added
    BugSomething is broken. Auto assigns a BugZero manager.
    DeployBlockerIndicates it should block deploying the API
    DeployBlockerCashThis issue or pull request should block deployment
    on Apr 10, 2025
  2. melvin-bot commented on Apr 10, 2025

    @melvin-bot

    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.

  3. melvin-bot commented on Apr 10, 2025

    @melvin-bot

    Triggered auto assignment to @mountiny (DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.

  4. melvin-bot commented on Apr 10, 2025

    @melvin-bot

    💬 A slack conversation has been started in #expensify-open-source

  5. github-actions commented on Apr 10, 2025

    @github-actions
    Contributor

    👋 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:

    1. Identify the pull request that introduced this issue and revert it.
    2. Find someone who can quickly fix the issue.
    3. Fix the issue yourself.
  6. removed
    DeployBlockerIndicates it should block deploying the API
    DeployBlockerCashThis issue or pull request should block deployment
    on Apr 10, 2025
  7. 26 remaining items

  8. melvin-bot commented on May 22, 2025

    @melvin-bot

    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!

  9. melvin-bot commented on Jul 18, 2025

    @melvin-bot

    @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.

  10. izarutskaya commented on Jul 22, 2025

    @izarutskaya

    Not repro on mWeb/Chrome

    0-02-01-bd72b26ae3914a10ede806d343e447c9e93a0308d12422d18003afd540f17f92_f71d44307339a668.1.mp4
  11. mountiny commented on Jul 22, 2025

    @mountiny
    Contributor

    I guess we can close now

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

BugSomething is broken. Auto assigns a BugZero manager.EngineeringExternalAdded to denote the issue can be worked on by a contributorWeeklyKSv2

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions