Skip to content

iPhone Duo - Rules - Tab carousel is cut off when Expense defaults tab is selected #107276

Open

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?: N/A - new feature, doesn't exist in prod
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:

Precondition:

  • Enable Rules.
  1. Launch Expensify app.
  2. Go to workspace settings > Rules.
  3. Scroll the tab carousel to the right.
    → Tab carousel extends full width (not cut off in vertical control area).
  4. Tap Expense defaults.
  5. Scroll the tab carousel to the right.
    → BUG 1: Tab carousel is cut off in vertical control area when Expense defaults is selected.
  6. Tap General tab.
  7. Scroll the tab carousel to the right.
  8. Tap Agents.
    → BUG 2: Tab carousel scroll position changes after tapping Agents.

Expected Result:

BUG 1: Tab carousel will not cut off in vertical control area when Expense defaults is selected.
BUG 2: Tab carousel scroll position will persist after tapping Agents.

Actual Result:

BUG 1: Tab carousel is cut off in vertical control area when Expense defaults is selected.
BUG 2: Tab carousel scroll position changes after tapping Agents.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7318001_1795016452821.ScreenRecording_11-18-2026_23-36-06_1.mp4

View all open jobs on GitHub

Applause Internal Information
Exported by: Chandana Kiran
Bug ID: 7318001

Issue OwnerCurrent Issue Owner: @war-in

Activity

  1. 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/69f98f0a16663667e24688980b4324bd1d802fbf963a6f82bf8b842ca2b6374f

  2. added
    DeployBlockerCashThis issue or pull request should block deployment
    BugSomething is broken. Auto assigns a BugZero manager.
    on Nov 18, 2026
  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. Chandkia24 commented on Nov 18, 2026

    @Chandkia24

    We couldn't reproduce this issue a second time because it is device-specific, and the iPhone Duo is the only one in the team.

  9. MelvinBot commented on Nov 18, 2026

    @MelvinBot
    Contributor

    Deploy-blocker investigation

    Recommendation: Do not revert yet. Keep the blocker pending targeted confirmation. The evidence suggests two potentially separate problems; neither was verified at runtime.

    1. Carousel clipping: likely related to the iPhone Duo safe-area changes

    “fix: add iPhone Duo support” shipped in the reported staging version, 9.5.41-0. Its safe-area changes plausibly explain why clipping differs between tabs:

    Confidence: medium as a hypothesis, not a confirmed cause. The affected table’s contents and native clipping behavior remain unverified.

    2. Scroll-position change: not established as a regression from that PR

    The selector lives inside conditionally rendered tab bodies, allowing tab changes to remount it and lose its previous offset. Additionally, pressing a tab intentionally scrolls it into view.

    Those implementations are unchanged between the inspected production and staging commits. The observed movement could therefore be pre-existing behavior or expected visibility adjustment.

    Decision needed

    Confirm on the reporting device whether:

    1. Clipping depends on Expense defaults containing rows.
    2. Selecting Agents loses a previously valid offset rather than merely revealing the selected tab.
    3. Any controls become inaccessible.

    QA could not reproduce a second time. No runtime verification was completed here. A web pass would not rule out native clipping because web safe-area handling is a no-op.

    If confirmed, favor a targeted fix over a broad revert. No sufficiently reliable, mechanically detectable review rule was identified yet.


    view run

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

    @mountiny
    Contributor

    Demoting as the Duo support is still evolving

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