Skip to content

[$250] Expense - Not here page opens after deleting expense #80663

Closed

Description

@lanitochka17

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.3.10-0
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from BrowserStack: #77948
Email or phone of affected tester (no customers): sjdiosjndoijdosjs@gmail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Mac 26.1 / Chrome
App Component: Money Requests

Action Performed:

  1. Go to staging.new.expensify.com
  2. Go to workspace chat.
  3. Create an expense.
  4. Open the expense report.
  5. Click on the header > Delete expense.
  6. Delete the expense.

Expected Result:

Report RHP will close.

Actual Result:

Not here page opens after deleting expense.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7059583_1769544497163.2.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~022016247151161706868
  • Upwork Job ID: 2016247151161706868
  • Last Price Increase: 2026-01-27
Issue OwnerCurrent Issue Owner: @sobitneupane

Activity

  1. added
    ExternalAdded to denote the issue can be worked on by a contributor
    BugSomething is broken. Auto assigns a BugZero manager.
    on Jan 27, 2026
  2. melvin-bot commented on Jan 27, 2026

    @melvin-bot

    You have been assigned to this deploy blocker because you recently merged this PR: #77948

  3. changed the title [-]Expense - Not here page opens after deleting expense[/-] [+][$250] Expense - Not here page opens after deleting expense[/+] on Jan 27, 2026
  4. melvin-bot commented on Jan 27, 2026

    @melvin-bot
  5. melvin-bot commented on Jan 27, 2026

    @melvin-bot

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

  6. added
    Help WantedApply this label when an issue is open to proposals by contributors
    on Jan 27, 2026
  7. melvin-bot commented on Jan 27, 2026

    @melvin-bot

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

  8. melvin-bot commented on Jan 27, 2026

    @melvin-bot

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

  9. 20 remaining items

  10. roryabraham commented on Jan 27, 2026

    @roryabraham
    Contributor

    Solution was merged. Thanks @abbasifaizan70 and @ZhenjaHorbach for being diligent to fix that regression quickly 🙇🏼

  11. PiyushChandra17 commented on Jan 27, 2026

    @PiyushChandra17
    Contributor

    @roryabraham I have one question here, if InteractionManager.runAfterInteractions is deprecated, should we use Navigation.setNavigateToMicroTaskQueue across all our codebases 🤔

    Find all places where we are using InteractionManager.runAfterInteractions and Replace with Navigation.setNavigateToMicroTaskQueue. Maybe this should be seperate issue then, Thoughts?

  12. ZhenjaHorbach commented on Jan 27, 2026

    @ZhenjaHorbach
    Contributor

    @roryabraham I have one question here, if InteractionManager.runAfterInteractions is deprecated, should we use Navigation.setNavigateToMicroTaskQueue across all our codebases 🤔

    Find all places where we are using InteractionManager.runAfterInteractions and Replace with Navigation.setNavigateToMicroTaskQueue. Maybe this should be seperate issue then, Thoughts?

    You can try to find information on Slack about it
    For example here
    As far as I remember, we don't have a single solution yet

  13. roryabraham commented on Jan 28, 2026

    @roryabraham
    Contributor

    #71913 was closed before it was fully resolved. Partially my fault, but I'm spread thin and we really need someone to champion the migration

  14. PiyushChandra17 commented on Jan 28, 2026

    @PiyushChandra17
    Contributor

    we really need someone to champion the migration

    @roryabraham I'd like to work on this ....

  15. roryabraham commented on Jan 28, 2026

    @roryabraham
    Contributor
  16. roryabraham commented on Jan 28, 2026

    @roryabraham
    Contributor

    we really need someone to champion the migration
    @roryabraham I'd like to work on this ....

    We're discussing internally.

  17. m-natarajan commented on Jan 28, 2026

    @m-natarajan

    This issue is reproducible on Windows 11 / Chrome in v9.3.10-3

    bandicam.2026-01-28.09-28-32-166.mp4
  18. ZhenjaHorbach commented on Jan 28, 2026

    @ZhenjaHorbach
    Contributor

    This issue is reproducible on Windows 11 / Chrome in v9.3.10-3

    bandicam.2026-01-28.09-28-32-166.mp4

    Strange
    It works well for me

    @abbasifaizan70
    Can you try to reproduce on staging?

    2026-01-28.08.08.33.mov
  19. abbasifaizan70 commented on Jan 28, 2026

    @abbasifaizan70
    Contributor
    Screen.Recording.2026-01-28.at.5.44.31.PM.mov

    @ZhenjaHorbach not able to reproduce that.

  20. IuliiaHerets commented on Jan 28, 2026

    @IuliiaHerets

    @abbasifaizan70 @roryabraham @ZhenjaHorbach original tester can't reproduce this issue anymore in the latest build

    Screen.Recording.2026-01-28.at.20.52.45.mp4
  21. ZhenjaHorbach commented on Jan 28, 2026

    @ZhenjaHorbach
    Contributor

    @abbasifaizan70 @roryabraham @ZhenjaHorbach original tester can't reproduce this issue anymore in the latest build

    Screen.Recording.2026-01-28.at.20.52.45.mp4

    Oh
    Good then😅
    Because I couldn't think of any reason why it was still reproducing
    Thanks for retesting!

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 contributorHourlyKSv2ReviewingHas a PR in review

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions