Skip to content

[Due for payment 2026-11-28] iPhone Duo - Current tab is not highlighted after opening Account and switching tab #107220

Closed

Description

@applause-bot

If you haven’t already, check out our contributing guidelines for onboarding. To join our Slack channel, fill out this form.


Version Number: 9.5.41-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: #104730
Email or phone of affected tester (no customers): joinsdjosjdojosijdiosnj@gmail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: iPhone Duo / iOS 27.2
App Component: Workspace Settings

Action Performed:

  1. Launch Expensify app.
  2. Go to Account.
    → Home tab remains selected.
  3. Tap Profile.
  4. Tap app back button.
  5. Open Workspaces tab.
  6. Open any tab.
    → Tab is not highlighted when opened.

Expected Result:

In Step 2, on Account page, Home tab will not be selected.
In Step 6, after opening Account and switching tab, the current tab will be highlighted.

Actual Result:

In Step 2, on Account page, Home tab remains selected.
In Step 6, after opening Account and switching tab, the current tab is not highlighted.

Workaround:

Unknown

Platforms:

  • Android: App
  • Android: mWeb Chrome
  • iOS: App
  • iOS: mWeb Safari
  • iOS: mWeb Chrome
  • Windows: Chrome
  • MacOS: Chrome Safari

Screenshots/Videos

Bug7317313_1794974128565.ScreenRecording_11-18-2026_11-51-44_1.mp4

View all open jobs on GitHub

Applause Internal Information
Exported by: Julia Ponikarchuk
Bug ID: 7317313

Issue OwnerCurrent Issue Owner: @truph01

Activity

  1. added
    DeployBlockerCashThis issue or pull request should block deployment
    BugSomething is broken. Auto assigns a BugZero manager.
    on Nov 18, 2026
  2. applause-bot commented on Nov 18, 2026

    @applause-bot
    Author

    While Applause doesn't embed attachments for this bug, here are the links for quick view:
    https://platform.applause.com/services/links/v1/external/91dce5b18f0f9291be9476eaf7ecaf9b056f76234601c3b229b2d9bccfb1543d

  3. expensify-chore-bot commented on Nov 18, 2026

    @expensify-chore-bot

    You have been assigned to this deploy blocker because you recently merged this PR: #104730

  4. expensify-chore-bot commented on Nov 18, 2026

    @expensify-chore-bot

    @mountiny @truph01 you have been assigned to this deploy blocker because you reviewed the offending PR: #104730

  5. expensify-chore-bot commented on Nov 18, 2026

    @expensify-chore-bot

    @war-in you have been assigned to this deploy blocker because you authored the offending PR: #104730

  6. expensify-chore-bot commented on Nov 18, 2026

    @expensify-chore-bot

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

  7. github-actions commented on Nov 18, 2026

    @github-actions
    Contributor

    👋 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.
  8. MelvinBot commented on Nov 18, 2026

    @MelvinBot
    Contributor

    Deploy blocker investigation

    “fix: add iPhone Duo support” is the leading suspect, but the exact cause remains unconfirmed. Recommend keeping the deploy blocked pending a targeted native comparison.

    Evidence

    Working hypothesis: Duo’s newly enabled vertical layout interacts incorrectly with that existing selection-hiding/restoration logic. This fits both Home remaining highlighted on Account and selection disappearing afterward, but the specific native failure has not been demonstrated.

    The selection-hiding patch itself is identical in production and the suspect PR’s merge, making it a possible underlying compatibility weakness rather than the newly introduced change.

    Recommended disposition

    Compare the exact reported flow on the same Duo/iOS build at the suspect PR’s parent (7e4a27a) and merge (881800a):

    Account → Profile → app back → Workspaces → another tab.

    If the parent passes and merge fails, revert the Duo-support PR before deployment unless a narrowly scoped fix passes the same checks, including selection restoration in both horizontal and vertical layouts. Avoid guessing additional private UIKit class names without inspecting the failing hierarchy.

    Verification limitation: No interactive reproduction was performed. Only web testing was authorized, and web cannot validate this UIKit-specific behavior. No code, labels, or assignments were changed.


    view run

  9. 1 remaining item

  10. war-in commented on Nov 18, 2026

    @war-in
    Contributor

    @jponikarchuk could we get a correct video?

  11. jponikarchuk commented on Nov 18, 2026

    @jponikarchuk

    @war-in Thank you. Edited

  12. melvin-bot commented on Nov 18, 2026

    @melvin-bot

    ⚠️ Looks like this issue was linked to a Deploy Blocker here

    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.

  13. added and removed
    DeployBlockerCashThis issue or pull request should block deployment
    on Nov 18, 2026
  14. mountiny commented on Nov 18, 2026

    @mountiny
    Contributor

    Demoting as the Duo support is still evolving

  15. changed the title [-]iPhone Duo - Current tab is not highlighted after opening Account and switching tab[/-] [+][Due for payment 2026-11-28] iPhone Duo - Current tab is not highlighted after opening Account and switching tab[/+] on Nov 21, 2026
  16. melvin-bot commented on Nov 21, 2026

    @melvin-bot

    @truph01

    The solution for this issue has been 🚀 deployed to production 🚀 in version 9.5.51-1 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:

    If no regressions arise, payment will be issued on 2026-11-28. 🎊

    The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the Contributor+ Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]. If no checklist is needed for this issue, you can click: [no checklist button]

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

BugSomething is broken. Auto assigns a BugZero manager.DailyKSv2Engineering

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions