[cp staging] Revert "Reset navigation when a copilot switches accounts" by linhvovan29546 · Pull Request #105551 · Expensify/App

linhvovan29546 · 2026-10-31T09:36:57Z

Explanation of Change

Reverts #105446 to fix the deploy blocker #105550.

Fixed Issues

$ #105550
PROPOSAL: N/A (revert)

Tests

N/A. This PR only reverts navigation changes

Verify that no errors appear in the JS console

Offline tests

N/A. This PR only reverts navigation changes

QA Steps

N/A. This PR only reverts navigation changes

Verify that no errors appear in the JS console

PR Author Checklist

Screenshots/Videos

Android: Native

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

codecov · 2026-10-31T09:42:04Z

Codecov Report

❌ Looks like you've decreased code coverage for some files. Please write tests to increase, or at least maintain, the existing level of code coverage. See our documentation here for how to interpret this table.

Files with missing lines	Coverage Δ
src/hooks/useAgentsTable.ts	`71.26% <100.00%> (ø)`
src/hooks/useSwitchToDelegator.ts	`77.50% <100.00%> (ø)`
.../Navigation/AppNavigator/withAgentAccessDenied.tsx	`87.80% <100.00%> (ø)`
src/libs/Navigation/Navigation.ts	`72.21% <ø> (-0.52%)`	⬇️
src/libs/Navigation/NavigationRoot.tsx	`83.87% <100.00%> (ø)`
...on/helpers/lastVisitedTabPathUtils/index.native.ts	`60.00% <ø> (-6.67%)`	⬇️
...avigation/helpers/lastVisitedTabPathUtils/index.ts	`0.00% <ø> (ø)`
src/pages/ProfilePage.tsx	`88.41% <100.00%> (ø)`
src/pages/settings/Agents/DynamicEditAgentPage.tsx	`95.04% <100.00%> (ø)`
src/libs/actions/Delegate.ts	`72.09% <66.66%> (-6.71%)`	⬇️
... and 1 more
... and 8 files with indirect coverage changes

melvin-bot · 2026-10-31T09:49:35Z

@ZhenjaHorbach Please copy/paste the Reviewer Checklist from here into a new comment on this PR and complete it. If you have the K2 extension, you can simply click: [this button]

chatgpt-codex-connector · 2026-10-31T09:49:38Z

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	⚠️ Failed 2026-10-31T10:11:01.807076Z We couldn’t complete this review. Comment `@codex review` to try again.	`1e6b77f`	Draft marked ready

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

Open a pull request for review
Mark a draft as ready
Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

ZhenjaHorbach · 2026-10-31T09:52:09Z

I can approve it to speed up merging a bit

ZhenjaHorbach · 2026-10-31T09:52:31Z

Reviewer Checklist

I have verified the author checklist is complete (all boxes are checked off).
I verified the correct issue is linked in the ### Fixed Issues section above
I verified testing steps are clear and they cover the changes made in this PR
- I verified the steps for local testing are in the Tests section
- I verified the steps for Staging and/or Production testing are in the QA steps section
- I verified the steps cover any possible failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
- I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
I checked that screenshots or videos are included for tests on all platforms
I included screenshots or videos for tests on all platforms
I verified that the composer does not automatically focus or open the keyboard on mobile unless explicitly intended. This includes checking that returning the app from the background does not unexpectedly open the keyboard.
I verified tests pass on all platforms & I tested again on:
- Android: HybridApp
- Android: mWeb Chrome
- iOS: HybridApp
- iOS: mWeb Safari
- MacOS: Chrome / Safari
If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
I verified proper code patterns were followed (see Reviewing the code)
- I verified that comments were added to code that is not self explanatory
- I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
- I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
I verified that this PR follows the guidelines as stated in the Review Guidelines
I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
If a new component is created I verified that:
- A similar component doesn't exist in the codebase
- All props are defined accurately
- The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
- The only data being stored in the state is data necessary for rendering and nothing else
- The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions
If a new CSS style is added I verified that:
- A similar style doesn't already exist
- The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG)
If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:
- I verified that all the inputs inside a form are aligned with each other.
- I added Design label and/or tagged @Expensify/design so the design team can review the changes.
If the PR adds or modifies the UI:
- I asked an AI agent to review the changes for accessibility issues and addressed its findings.
- I tested with a screen reader (VoiceOver on macOS) and verified all new/changed elements are reachable with a logical focus order.
- I verified all new/changed elements have meaningful accessible names and roles.
- I verified state changes are announced (e.g. checked/unchecked, expanded/collapsed, selected).
For any bug fix or new feature in this PR, I verified that sufficient unit tests are included to prevent regressions in this flow.
If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

Android: HybridApp

Android: mWeb Chrome

iOS: HybridApp

iOS: mWeb Safari

MacOS: Chrome / Safari

github-actions · 2026-11-02T13:09:16Z

🚧 JS00001 has triggered a test Expensify/App build. You can view the workflow run here.

github-actions · 2026-11-02T13:13:40Z

🧪🧪 Use the links below to test this adhoc build on Android, iOS, and Web. Happy testing! 🧪🧪
Built from App PR #105551 with the pinned Mobile-Expensify submodule.

Android 🤖	iOS 🍎
https://ad-hoc-expensify-cash.s3.us-east-1.amazonaws.com/rock-artifacts/ad-hoc/rock-android-Adhoc-5f5488e9-f89e1f8-9821650952510ae53cb46b12d455781c778ea4b0/index.html	https://ad-hoc-expensify-cash.s3.us-east-1.amazonaws.com/rock-artifacts/ad-hoc/rock-ios-device-AdHoc-5f5488e9-f89e1f8-85e99c739d1014c214de426c5bb692615b265130/index.html

Web 🕸️
https://105551.pr-testing.expensify.com

👀 View the workflow run that generated this build 👀

OSBotify · 2026-11-02T13:13:41Z

✋ This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

…esetNavigationOnCopilotSwitch [cp staging] Revert "Reset navigation when a copilot switches accounts" (cherry picked from commit 5f5488e) (cherry-picked to staging by Beamanator)

os-botify · 2026-11-02T14:35:41Z

🔁 Filed a Staging retest request for deploy blockers #105550 after this PR was cherry-picked to staging.

OSBotify · 2026-11-02T14:38:08Z

🚀 Cherry-picked to staging by https://github.com/Beamanator in version: 9.5.27-2 🚀

platform	result
🕸 web 🕸	success ✅
🤖 android 🤖	success ✅
🍎 iOS 🍎	success ✅

OSBotify · 2026-11-02T18:24:23Z

🚀 Deployed to production by https://github.com/blimpich in version: 9.5.27-2 🚀

platform	result
🕸 web 🕸	success ✅
🤖 android 🤖	success ✅
🍎 iOS 🍎	success ✅

Bundle Size Analysis (Sentry):

Android
iOS

Revert "Reset navigation when a copilot switches accounts"

1e6b77f

melvin-bot Bot assigned linhvovan29546 Oct 31, 2026

linhvovan29546 marked this pull request as ready for review October 31, 2026 09:49

linhvovan29546 requested review from a team as code owners October 31, 2026 09:49

melvin-bot Bot requested review from ZhenjaHorbach and dylanexpensify and removed request for a team October 31, 2026 09:49

linhvovan29546 mentioned this pull request Oct 31, 2026

[Due for payment 2026-11-09] Copilot-After returning from copilot, back button changes URL but user remains on same page #105550

Closed

1 of 7 tasks

linhvovan29546 requested review from JS00001 and marcaaron and removed request for ZhenjaHorbach and dylanexpensify October 31, 2026 09:51

ZhenjaHorbach approved these changes Oct 31, 2026

View reviewed changes

JS00001 changed the title ~~Revert "Reset navigation when a copilot switches accounts"~~ [cp staging] Revert "Reset navigation when a copilot switches accounts" Nov 2, 2026

JS00001 approved these changes Nov 2, 2026

View reviewed changes

JS00001 merged commit 5f5488e into Expensify:main Nov 2, 2026
48 of 52 checks passed

OSBotify added the CP Staging marks PRs that have been CP'd to staging label Nov 2, 2026

OSBotify mentioned this pull request Nov 2, 2026

Deploy Checklist: New Expensify 2026-10-31 #105544

Closed

77 tasks done

Navigation Menu

Repository navigation

[cp staging] Revert "Reset navigation when a copilot switches accounts" - #105551

[cp staging] Revert "Reset navigation when a copilot switches accounts"#105551
JS00001 merged 1 commit into
Expensify:mainfrom
linhvovan29546:revert-105446-claude-resetNavigationOnCopilotSwitch

linhvovan29546 commented Oct 31, 2026 •

edited

Loading

Uh oh!

codecov Bot commented Oct 31, 2026 •

edited by github-actions Bot

Loading

Uh oh!

melvin-bot Bot commented Oct 31, 2026

Uh oh!

chatgpt-codex-connector Bot commented Oct 31, 2026 •

edited

Loading

Uh oh!

ZhenjaHorbach commented Oct 31, 2026

Uh oh!

ZhenjaHorbach commented Oct 31, 2026

Uh oh!

Uh oh!

github-actions Bot commented Nov 2, 2026

Uh oh!

github-actions Bot commented Nov 2, 2026

Uh oh!

OSBotify commented Nov 2, 2026

Uh oh!

os-botify Bot commented Nov 2, 2026

Uh oh!

OSBotify commented Nov 2, 2026

Uh oh!

OSBotify commented Nov 2, 2026

Uh oh!

Reviewers

Uh oh!

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants

Conversation

linhvovan29546 commented Oct 31, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Explanation of Change

Fixed Issues

Tests

Offline tests

QA Steps

PR Author Checklist

Screenshots/Videos

Uh oh!

codecov Bot commented Oct 31, 2026 • edited by github-actions Bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Codecov Report

Uh oh!

melvin-bot Bot commented Oct 31, 2026

Uh oh!

chatgpt-codex-connector Bot commented Oct 31, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Codex Review Summary

Uh oh!

ZhenjaHorbach commented Oct 31, 2026

Uh oh!

ZhenjaHorbach commented Oct 31, 2026

Reviewer Checklist

Screenshots/Videos

Uh oh!

Uh oh!

github-actions Bot commented Nov 2, 2026

Uh oh!

github-actions Bot commented Nov 2, 2026

Uh oh!

OSBotify commented Nov 2, 2026

Uh oh!

os-botify Bot commented Nov 2, 2026

Uh oh!

OSBotify commented Nov 2, 2026

Uh oh!

OSBotify commented Nov 2, 2026

Uh oh!

Reviewers

Uh oh!

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants

linhvovan29546 commented Oct 31, 2026 •

edited

Loading

codecov Bot commented Oct 31, 2026 •

edited by github-actions Bot

Loading

chatgpt-codex-connector Bot commented Oct 31, 2026 •

edited

Loading