[sumo-slonik]

Explanation of Change

With the Insights beta, native Account keeps the tab bar with no item selected and no back arrow, like mWeb.

• bottom-tabs patch 005: Account is drawn inside the first visible tab (Home), which stays natively selected but is drawn unselected. Tapping any tab leaves Account.
• react-native-screens patch 007: iOS prop that hides the iOS 26 liquid glass selection; on Android the selected label is not bold while the indicator is transparent.
• App: removes the Account back arrow. The Android back button still returns to the previous tab, or Home after a relaunch.

Known limitation: VoiceOver and TalkBack may still announce Home as selected while Account is shown.

Fixed Issues

$ #104197
PROPOSAL: N/A

Tests

With the insightsPage beta on, narrow layout, iOS and Android native:

1. On Inbox, tap the avatar. Verify Account shows the tab bar with no item selected and no back arrow.
2. Tap Inbox. Verify Inbox opens and is selected right away.
3. Open Account again and tap Home. Verify Home opens selected.
4. On Android, open Account, kill and relaunch the app, then press the back button. Verify Home opens.
5. Without the beta, verify Account is a selected tab item.

• Verify that no errors appear in the JS console

Offline tests

Same as Tests.

QA Steps

Same as Tests.

• Verify that no errors appear in the JS console

PR Author Checklist

• I linked the correct issue in the ### Fixed Issues section above
• I wrote clear testing steps that cover the changes made in this PR
  • I added steps for local testing in the Tests section
  • I added steps for the expected offline behavior in the Offline steps section
  • I added steps for Staging and/or Production testing in the QA steps section
  • I added steps to cover 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 tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).
• I included screenshots or videos for tests on all platforms
• I ran the tests on all platforms & verified they passed on:
  • Android: Native
  • Android: mWeb Chrome
  • iOS: Native
  • iOS: mWeb Safari
  • MacOS: Chrome / Safari
• I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
• I verified any copy / text that was added to the app 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 tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
• If new assets were added or existing ones were modified, I verified that:
  • The assets are optimized and compressed (for SVG files, run npm run compress-svg)
  • The assets load correctly across all supported platforms.
• 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).
• I added unit tests for any new feature or bug fix in this PR to help automatically prevent regressions in this user 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.

Screenshots/Videos

Android: Native

Screen.Recording.2026-10-20.at.21.13.24.mov

Android: mWeb Chrome

N/A, the change is native only.

iOS: Native

Screen.Recording.2026-10-20.at.21.13.08.mov

iOS: mWeb Safari

N/A, the change is native only.

MacOS: Chrome / Safari

N/A, the change is native only.

[github-actions]

⚠️ This PR is possibly changing native code and/or updating libraries, it may cause problems with HybridApp. Please check if any patch updates are required in the HybridApp repo and run an AdHoc build to verify that HybridApp will not break. Ask Contributor Plus for help if you are not sure how to handle this. ⚠️

[codecov]

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 Δ
...Content/useTabRootScreenWrapperProps/index.ios.tsx	85.71% <100.00%> (-14.29%)	⬇️
src/components/Navigation/TopBar.tsx	100.00% <100.00%> (ø)
src/components/Navigation/TopBarWithLoadingBar.tsx	100.00% <100.00%> (ø)
...gators/NativeTabNavigator/useNativeTabNavigator.ts	100.00% <100.00%> (ø)
src/pages/settings/InitialSettingsPage.tsx	98.07% <ø> (+14.49%)	⬆️
...ent/useTabRootScreenWrapperProps/index.android.tsx	0.00% <0.00%> (ø)
... and 12 files with indirect coverage changes

[chatgpt-codex-connector]

Codex Review Summary

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

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-10-21T17:00:18.699348Z	88ede4f	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.

[melvin-bot]

@shawnborton @ZhenjaHorbach One of you needs to 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]