Description
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: v9.3.51-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: #81808
Email or phone of affected tester (no customers): expensify416+da2@gmail.com
Issue reported by: Applause Internal Team
Bug source: Pull Request QA execution
Device used: macOS chrome
App Component: Other
Action Performed:
- Go to https://staging.new.expensify.com/
- Sign up with a new account
- Complete onboarding selecting "Something else" and don't create any workspace
- Once on "Home" tap on FAB and select "Start Chat"
- Select "Room"
- Tap on "Learn More" button
- Tap on "New Workspace"
- Complete creation flow
- Once on new workspace's profile, press browsers back button to return to workspaces list
- Press browser's back button again
Expected Result:
Step 8: user should be returned back to workspace list page
Step 9: user should be returned back to Room creation flow in RHP
Actual Result:
Step 8: User is redirected back to Home page
Step 9: URL changes without page change
Workaround:
Unknown
Platforms:
- Android: App
- Android: mWeb Chrome
- iOS: App
- iOS: mWeb Safari
- iOS: mWeb Chrome
- Windows: Chrome
- MacOS: Chrome / Safari
Screenshots/Videos
bug.mp4
Issue Owner
Current Issue Owner: @ChavdaSachinIssue Owner
Current Issue Owner: @WojtekBomanMetadata
Metadata
Labels
Type
Projects
- StatusShow more project fieldsDone
Activity
melvin-bot commentedon Mar 31, 2026
You have been assigned to this deploy blocker because you recently merged this PR: #81808
melvin-bot commentedon Mar 31, 2026
💬 A slack conversation has been started in #expensify-open-source
github-actions commentedon Mar 31, 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 31, 2026
🔍 Investigation Summary
Classification: Frontend bug
Causing PR: #81808 - "fix: Workspace - Creating workspace from room´s Learn More and returning, leads to Share Code" by @TaduJR (High confidence)
Related Issues: #71803 (original issue that PR #81808 fixed)
Recommendation: REVERT
PR #81808 should be reverted because it introduces a regression on web platforms. While the fix works correctly for native apps, it breaks browser back button navigation on web.
Labels: No label changes - keeping
DeployBlockerCashsince this is an App PR that needs to be reverted📋 Detailed Analysis
Evidence
Verification
I verified PR #81808 modifies these navigation-related files:
src/libs/Navigation/AppNavigator/createRootStackNavigator/GetStateForActionHandlers.ts- Core navigation logicsrc/libs/Navigation/helpers/shouldStripRHPOnFullscreenPush/index.native.ts- Native behavior (strips RHP)src/libs/Navigation/helpers/shouldStripRHPOnFullscreenPush/index.ts- Web behavior (does NOT strip RHP)The PR introduces platform-specific logic in
handlePushFullscreenActionthat strips the RHP (Right Hand Panel) before pushing fullscreen screens.Root Cause
PR #81808 fixed issue #71803 where on Android native app, the back button led to "Share Code" instead of the room creation page. The fix strips the RHP from the navigation stack before pushing WORKSPACES_LIST, preventing the orphaned modal issue.
However, the fix uses platform-specific exports:
index.native.ts):shouldStripRHPOnFullscreenPush = true- RHP is stripped before pushing fullscreenindex.ts):shouldStripRHPOnFullscreenPush = false- RHP is preserved (to avoid triggeringhistory.back())On web, when the RHP is not stripped, the navigation stack becomes:
When the user creates a workspace and presses the browser back button, the RHP remaining in the stack causes incorrect navigation behavior. The browser history includes the RHP route, which interferes with the expected back navigation flow (workspace overview → workspace list → room creation).
The PR author correctly identified that calling
dismissModalon web would triggerhistory.back()viauseLinking, but the solution of not stripping the RHP at all on web creates a different regression with browser back button handling.vincdargento commentedon Apr 1, 2026
Culprit PR was not identified, the issue is reproducible in every snapshot build of the #86774
MelvinBot commentedon Apr 1, 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/23824945091
truph01 commentedon Apr 1, 2026
@MelvinBot I’m able to reproduce this issue after reverting the changes introduced in #81808.
If you review that PR, the new logic applies only to native platforms and does not affect the web. However, this issue is reproducible on the web, so it’s unlikely that #81808 is the root cause of this bug.
69 remaining items
ChavdaSachin commentedon Aug 14, 2026
No Checklist Needed
Not a regression, just an improvement.
cc. @mallenexpensify
melvin-bot commentedon Aug 17, 2026
@ChavdaSachin Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!
mallenexpensify commentedon Aug 18, 2026
@ChavdaSachin plz provide test case steps in case an update is needed. We always want to err on the side of create issues for the QA team, they can make the final call on what's needed.
quinthar commentedon Aug 19, 2026
Approved $250 to @ChavdaSachin
melvin-bot commentedon Aug 19, 2026
@ChavdaSachin Eep! 4 days overdue now. Issues have feelings too...
mallenexpensify commentedon Aug 19, 2026
@ChavdaSachin plz provide test case steps in case an update is needed. We always want to err on the side of create issues for the QA team, they can make the final call on what's needed.
ChavdaSachin commentedon Aug 19, 2026
Test steps
m-natarajan commentedon Aug 20, 2026
@ChavdaSachin This is regarding the regression test proposal
Step7: "I'm just looking around" on the Purpose step is not displayed during onboarding, Is this one expected or potential issue?