You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
iPhone Duo - Rules - Tab carousel is cut off when Expense defaults tab is selected #107276
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.
Launch Expensify app.
Go to workspace settings > Rules.
Scroll the tab carousel to the right.
→ Tab carousel extends full width (not cut off in vertical control area).
Tap Expense defaults.
Scroll the tab carousel to the right.
→ BUG 1: Tab carousel is cut off in vertical control area when Expense defaults is selected.
Tap General tab.
Scroll the tab carousel to the right.
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.
👋 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:
Identify the pull request that introduced this issue and revert it.
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:
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:
Clipping depends on Expense defaults containing rows.
Selecting Agents loses a previously valid offset rather than merely revealing the selected tab.
Activity
applause-bot commentedon Nov 18, 2026
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
expensify-chore-bot commentedon Nov 18, 2026
You have been assigned to this deploy blocker because you recently merged this PR: #104730
expensify-chore-bot commentedon Nov 18, 2026
@mountiny @truph01 you have been assigned to this deploy blocker because you reviewed the offending PR: #104730
expensify-chore-bot commentedon Nov 18, 2026
@war-in you have been assigned to this deploy blocker because you authored the offending PR: #104730
expensify-chore-bot commentedon Nov 18, 2026
💬 A slack conversation has been started in #expensify-open-source
github-actions commentedon Nov 18, 2026
👋 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:
Chandkia24 commentedon Nov 18, 2026
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.
MelvinBot commentedon Nov 18, 2026
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:
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
mountiny commentedon Nov 18, 2026
Demoting as the Duo support is still evolving