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
[Due for payment 2026-11-25] 107193 iPhone Duo - Tab carousel on Workflows does not extend to vertical control area like Rules #107272
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 and Workflows.
Launch Expensify app.
Go to workspace settings > Rules.
Scroll the tab carousel.
→ Carousel extends to vertical control area on the right.
Tap app back button.
Go to workspace settings > Workflows.
Scroll the tab carousel.
→ Carousel stops before vertical control area on the right.
Expected Result:
Tab carousel on Workflows and Rules should have the same behavior.
Actual Result:
On Rules page, tab carousel extends to vertical control area on the right.
On Workspaces page, tab carousel stops before vertical control area on the right.
👋 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.
Likely introducing PR:fix: add iPhone Duo support. Confidence: medium—the code explains the inconsistency, but the native-device behavior remains unconfirmed.
What is the root cause of that problem?
The new safe-area handling expands scroll views using negative margins without adjusting explicitly constrained widths. Workflows uses a width: 100% outer scroll view; Rules General uses a flex-sized one. This can leave Workflows’ carousel clipped earlier than Rules’.
What changes do you think we should make in order to solve the problem?
Prefer a targeted roll-forward over reverting broad Duo support, conditional on reproduction. Verify Workflows’ viewport sizing on the affected device, then evaluate releasing the explicit width only when safe-area expansion is active. Check both carousel visibility and native-control interaction.
Recommendation: retain the blocker pending device verification and design confirmation.
What alternative solutions did you explore?
Making Rules clip like Workflows conflicts with documented design intent. A full revert is broader than the suspected sizing defect warrants. A transient native-layout issue remains possible.
Suggested review safeguard: Flag negative-margin viewport expansion that preserves fixed or percentage widths without an explicit sizing policy.
Next Steps for Contributor+ team: To accept: After device confirmation, @MelvinBot implement [this](https://github.com/Expensify/App/issues/107272) to create a draft PR. To refine:@MelvinBot <your feedback> To reject: Explain why you are rejecting Melvin's proposal.
changed the title [-]iPhone Duo - Tab carousel is different on Workflows and Rules page[/-][+]107193 iPhone Duo - Tab carousel on Workflows does not extend to vertical control area like Rules[/+]on Nov 18, 2026
changed the title [-]107193 iPhone Duo - Tab carousel on Workflows does not extend to vertical control area like Rules[/-][+][Due for payment 2026-11-25] 107193 iPhone Duo - Tab carousel on Workflows does not extend to vertical control area like Rules[/+]on Nov 18, 2026
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.5.41-2 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-25. 🎊
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]
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/dc88827c95917a34442fbe3486b247606e98d2771380f3ebdd8334ad5ee785f8
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
Proposal
Likely introducing PR: fix: add iPhone Duo support. Confidence: medium—the code explains the inconsistency, but the native-device behavior remains unconfirmed.
What is the root cause of that problem?
The new safe-area handling expands scroll views using negative margins without adjusting explicitly constrained widths. Workflows uses a
width: 100%outer scroll view; Rules General uses a flex-sized one. This can leave Workflows’ carousel clipped earlier than Rules’.Importantly, Rules extending into the safe zone may be correct: design explicitly requested horizontally scrolling content remain visible there. Workflows stopping early is therefore the stronger suspected defect.
Supporting evidence
w100.width: 'auto'.What changes do you think we should make in order to solve the problem?
Prefer a targeted roll-forward over reverting broad Duo support, conditional on reproduction. Verify Workflows’ viewport sizing on the affected device, then evaluate releasing the explicit width only when safe-area expansion is active. Check both carousel visibility and native-control interaction.
This is not yet a validated fix. The reporter could not reproduce the issue again. No interactive testing was performed; the web safe-area implementation is a no-op, so web verification cannot establish the reported native behavior.
Recommendation: retain the blocker pending device verification and design confirmation.
What alternative solutions did you explore?
Making Rules clip like Workflows conflicts with documented design intent. A full revert is broader than the suspected sizing defect warrants. A transient native-layout issue remains possible.
Suggested review safeguard: Flag negative-margin viewport expansion that preserves fixed or percentage widths without an explicit sizing policy.
Next Steps for Contributor+ team:
To accept: After device confirmation,
@MelvinBot implement [this](https://github.com/Expensify/App/issues/107272)to create a draft PR.To refine:
@MelvinBot <your feedback>To reject: Explain why you are rejecting Melvin's proposal.
view run
[-]iPhone Duo - Tab carousel is different on Workflows and Rules page[/-][+]107193 iPhone Duo - Tab carousel on Workflows does not extend to vertical control area like Rules[/+][-]107193 iPhone Duo - Tab carousel on Workflows does not extend to vertical control area like Rules[/-][+][Due for payment 2026-11-25] 107193 iPhone Duo - Tab carousel on Workflows does not extend to vertical control area like Rules[/+]melvin-bot commentedon Nov 18, 2026
@truph01
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.5.41-2 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-25. 🎊
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]