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
[$250] Expense - Not here page opens after deleting expense #80663
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
changed the title [-]Expense - Not here page opens after deleting expense[/-][+][$250] Expense - Not here page opens after deleting expense[/+]on Jan 27, 2026
@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?
@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
Activity
melvin-bot commentedon Jan 27, 2026
You have been assigned to this deploy blocker because you recently merged this PR: #77948
[-]Expense - Not here page opens after deleting expense[/-][+][$250] Expense - Not here page opens after deleting expense[/+]melvin-bot commentedon Jan 27, 2026
Job added to Upwork: https://www.upwork.com/jobs/~022016247151161706868
melvin-bot commentedon Jan 27, 2026
💬 A slack conversation has been started in #expensify-open-source
melvin-bot commentedon Jan 27, 2026
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.melvin-bot commentedon Jan 27, 2026
Triggered auto assignment to Contributor-plus team member for initial proposal review - @sobitneupane (
External)20 remaining items
roryabraham commentedon Jan 27, 2026
Solution was merged. Thanks @abbasifaizan70 and @ZhenjaHorbach for being diligent to fix that regression quickly 🙇🏼
PiyushChandra17 commentedon Jan 27, 2026
@roryabraham I have one question here, if
InteractionManager.runAfterInteractionsis deprecated, should we useNavigation.setNavigateToMicroTaskQueueacross all our codebases 🤔Findall places where we are usingInteractionManager.runAfterInteractionsandReplacewithNavigation.setNavigateToMicroTaskQueue. Maybe this should be seperate issue then, Thoughts?ZhenjaHorbach commentedon Jan 27, 2026
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
roryabraham commentedon Jan 28, 2026
#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
PiyushChandra17 commentedon Jan 28, 2026
@roryabraham I'd like to work on this ....
roryabraham commentedon Jan 28, 2026
Requested retest: https://expensify.slack.com/archives/C09V78U42D8/p1769565937511589
roryabraham commentedon Jan 28, 2026
We're discussing internally.
m-natarajan commentedon Jan 28, 2026
This issue is reproducible on Windows 11 / Chrome in v9.3.10-3
bandicam.2026-01-28.09-28-32-166.mp4
ZhenjaHorbach commentedon Jan 28, 2026
Strange
It works well for me
@abbasifaizan70
Can you try to reproduce on staging?
2026-01-28.08.08.33.mov
abbasifaizan70 commentedon Jan 28, 2026
Screen.Recording.2026-01-28.at.5.44.31.PM.mov
@ZhenjaHorbach not able to reproduce that.
IuliiaHerets commentedon Jan 28, 2026
@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
ZhenjaHorbach commentedon Jan 28, 2026
Oh
Good then😅
Because I couldn't think of any reason why it was still reproducing
Thanks for retesting!