Android - Copilot - Copilot can access member's chat history which leads to not here page

[IuliiaHerets]

If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!

---

Version Number: 9.0.98-0
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: Yes, reproducible on both
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): [email protected]
Issue reported by: Applause Internal Team
Device used: Samsung Galaxy Z Fold 4 / Android 14
App Component: Other

Action Performed:

Precondition:

• User has access to another member's account.
• User has at least one workspace.

1. Launch ND or hybrid app.
2. Go to workspace chat.
3. Tap on the report header.
4. Tap Go to workspace.
5. Tap on profile icon on the bottom bar.
6. Open account switcher.
7. Select another account.
8. Tap device back button.
9. Tap device back button again.

Expected Result:

The copilot will not be able to access the other member's chat history via device back button.

Actual Result:

The copilot is able to access the other member's chat history via device back button, which leads to not here page.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug6741602_1739432740094.Screen_Recording_20250213_153643_Expensify.mp4

View all open jobs on GitHub

[melvin-bot]

Triggered auto assignment to @adelekennedy (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]

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

[github-actions]

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

[melvin-bot]

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

[IuliiaHerets]

Prod has another behavior

screen-20250213-101432.mp4

[mountiny]

This will most likely be related to the navigation changes https://expensify.slack.com/archives/C01GTK53T8Q/p1739435484596829?thread_ts=1739328522.587109&cid=C01GTK53T8Q but I am not sure if I understand the core issue here. You can also change to the copilot in production but you need to go to the settings page from outside of the workspace detail page, what happens then when you go back?

[parasharrajat]

I believe it is expected behavior. We are not able to access the chat history. Browser still has old navigation history after you switch to copilot and when you go back to those old reports, it will show not here as those chats belonged to the old account which looks good to me. This is the same as accessing a random chat via URL.

I don't think we can clear the whole navigation stack of the user.

[WojtekBoman]

I agree with @parasharrajat, it's a new flow where visited chat screens remain in the navigation history and we can go back to them after switching the account, I am not sure if we should clear nav history after switching the account, because I assume that if we had access to the previous account chats we would like to be able to go back to them, so it's a more complex case.

[mountiny]

Cool, I agree with the reasoning here, thank you !