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
Expense - New report opens and closes after creating new report #86544
Version Number: 9.3.50-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:#85570 Email or phone of affected tester (no customers):sdjsoidnsjoidjiosjnioj1@gmail.com Issue reported by: Applause Internal Team Bug source: Exploratory - Significant User Experience Deterioration Device used: Mac 26.2 / Chrome App Component: Money Requests
Action Performed:
Go to staging.new.expensify.com
Log in with new account.
Create a workspace.
Go to Inbox.
Open FAB > Create report.
Go to Home tab.
Open FAB > Create report.
Click Create report.
Expected Result:
New report will open.
Actual Result:
New report opens and closes and app returns to workspace chat.
👋 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.
Classification: Frontend bug Causing PR: #85570 - "Show Create Report CTA for users without a workspace" by @mukhrr (High confidence) Related Issues: None found
Recommendation: REVERT
The PR introduced a Navigation.goBack() call that executes before navigating to the newly created report, causing the report to open and immediately close. This affects the create report flow when users go through the upgrade path.
Labels: Keeping DeployBlockerCash (this is an App/frontend bug that blocks the mobile deploy)
📋 Detailed Analysis
Evidence
PR #85570 modified the report creation flow by refactoring the logic into a new useCreateReportAction hook. The PR also modified IOURequestStepUpgrade.tsx which handles the upgrade flow when users without a workspace try to create a report.
The bug is reproducible only on staging (where PR #85570 is deployed) and not on production (where it is not yet deployed).
Verification
The affected file is /home/runner/_work/App/App/src/pages/iou/request/step/IOURequestStepUpgrade.tsx, specifically lines 128-145 in the CONST.UPGRADE_PATHS.REPORTS case.
PR #85570 modified this file (confirmed in the PR files list), and this file handles the exact flow described in the reproduction steps: creating a workspace and then creating a report.
Root Cause
In IOURequestStepUpgrade.tsx, the code calls Navigation.goBack() unconditionally at line 129, before the conditional logic that creates and navigates to the new report (lines 130-139). This causes the following sequence:
User clicks "Create report"
Navigation.goBack() executes, popping the navigation stack back to workspace chat
createNewReport() is called and creates the report
navigateWithMicrotask() attempts to navigate to the new report
The navigation state is already back at workspace chat, causing the new report to open and immediately close
The fix should move the Navigation.goBack() call to only execute in the branches where navigation to a new report does NOT occur, or remove it entirely from the report creation branch.
I ran out of time before I could finish helping you. This usually means the task was too complex or I got stuck exploring. Please try again with a more specific request or post in the #melvinbot-ai.
Activity
melvin-bot commentedon Mar 27, 2026
You have been assigned to this deploy blocker because you recently merged this PR: #85570
melvin-bot commentedon Mar 27, 2026
💬 A slack conversation has been started in #expensify-open-source
github-actions commentedon Mar 27, 2026
👋 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:
OSBotify commentedon Mar 27, 2026
🔍 Investigation Summary
Classification: Frontend bug
Causing PR: #85570 - "Show Create Report CTA for users without a workspace" by @mukhrr (High confidence)
Related Issues: None found
Recommendation: REVERT
The PR introduced a Navigation.goBack() call that executes before navigating to the newly created report, causing the report to open and immediately close. This affects the create report flow when users go through the upgrade path.
Labels: Keeping
DeployBlockerCash(this is an App/frontend bug that blocks the mobile deploy)📋 Detailed Analysis
Evidence
PR #85570 modified the report creation flow by refactoring the logic into a new
useCreateReportActionhook. The PR also modifiedIOURequestStepUpgrade.tsxwhich handles the upgrade flow when users without a workspace try to create a report.The bug is reproducible only on staging (where PR #85570 is deployed) and not on production (where it is not yet deployed).
Verification
The affected file is
/home/runner/_work/App/App/src/pages/iou/request/step/IOURequestStepUpgrade.tsx, specifically lines 128-145 in theCONST.UPGRADE_PATHS.REPORTScase.PR #85570 modified this file (confirmed in the PR files list), and this file handles the exact flow described in the reproduction steps: creating a workspace and then creating a report.
Root Cause
In
IOURequestStepUpgrade.tsx, the code callsNavigation.goBack()unconditionally at line 129, before the conditional logic that creates and navigates to the new report (lines 130-139). This causes the following sequence:Navigation.goBack()executes, popping the navigation stack back to workspace chatcreateNewReport()is called and creates the reportnavigateWithMicrotask()attempts to navigate to the new reportThe fix should move the
Navigation.goBack()call to only execute in the branches where navigation to a new report does NOT occur, or remove it entirely from the report creation branch.Fix report opening and immediately closing on second create
MelvinBot commentedon Mar 27, 2026
I ran out of time before I could finish helping you. This usually means the task was too complex or I got stuck exploring. Please try again with a more specific request or post in the #melvinbot-ai.
Run details: https://github.com/Expensify/Expensify/actions/runs/23650113075
m-natarajan commentedon Mar 27, 2026
Repro v9.3.50-2 web chrome
Screen.Recording.2026-03-28.at.01.35.23.mp4
marcaaron commentedon Mar 27, 2026
I'm confused. Did the revert fix it or not ?
marcaaron commentedon Mar 27, 2026
Ok I'm reverting this PR since it was linked to quite a few blockers it seems. I will alert QA.
mukhrr commentedon Mar 28, 2026
@marcaaron could you pls assign me here?! thanks
mukhrr commentedon Mar 28, 2026
Btw, PR fixing this issue is ready
melvin-bot commentedon Mar 30, 2026
If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results.
If a regression has occurred and you are the assigned CM follow the instructions here.
If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future.
m-natarajan commentedon Mar 31, 2026
Reproduced, Windows 11 / Chrome, v9.3.50-4
new.report.mp4
jasperhuangg commentedon Mar 31, 2026
still happens with that revert cc @marcaaron
mukhrr commentedon Mar 31, 2026
oh then @marcaaron could you pls assign me here. THis PR fixes issue
jasperhuangg commentedon Mar 31, 2026
hold up, why did the CP message post 8 hours after QA checked it?? Did the CP fail? I'm gonna ask for another retest just to be safe.
m-natarajan commentedon Mar 31, 2026
Not Repro, Windows 10/ Chrome, v9.3.50-8
repro.-.86544.mp4