Description
If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!
Version Number: V9.3.54
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: #85229
Email or phone of affected tester (no customers): dreamnitethedragon+vegst@gmail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Redmi note 10s android 13
App Component: Workspace Settings
Action Performed:
- Launch app
- Open an expense
- Tap date
- Turn to landscape
- Note side arrow to navigate to next month
Expected Result:
Side arrow to navigate to next month must not be hidden behind navigation bar.
Actual Result:
Side arrow to navigate to next month is hidden behind navigation bar.
Workaround:
Unknown
Platforms:
- Android: App
- Android: mWeb Chrome
- iOS: App
- iOS: mWeb Safari
- iOS: mWeb Chrome
- Windows: Chrome
- MacOS: Chrome / Safari
Screenshots/Videos
Bug7124608_1775640085641.Screenrecorder-2026-04-08-14-48-11-565.mp4
Issue Owner
Current Issue Owner: @rushatgabhaneMetadata
Metadata
Labels
Type
Projects
- StatusShow more project fieldsDone
Activity
melvin-bot commentedon Apr 8, 2026
@mjasikowski recently merged #85229, but they are OOO right now, so I'll auto-assign someone else.
melvin-bot commentedon Apr 8, 2026
Triggered auto assignment to @deetergp (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.melvin-bot commentedon Apr 8, 2026
💬 A slack conversation has been started in #expensify-open-source
github-actions commentedon Apr 8, 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:
MelvinBot commentedon Apr 8, 2026
Proposal
What is the root cause of that problem?
The date picker opens as a
BOTTOM_DOCKEDmodal on native (PopoverWithMeasuredContent/index.tsx:34). In landscape on Android, the modal container haswidth: '100%'andoverflow: 'hidden'(ModalStyleUtils.ts:230-234), which refers to the full-screen window (including behind system bars, sincestatusBarTranslucentis enabled).The calendar header's month navigation arrows are positioned with
justifyContentEndandmrn2(marginRight: -8) (CalendarPicker/index.tsx:219), pushing them as close to the right content edge as possible.On Android devices with 3-button navigation (like the Redmi Note 10s), the system navigation bar moves to the side of the screen in landscape mode. While
getModalPaddingStylesappliespaddingRightfrom safe area insets (styles/utils/index.ts:654), theNavigationBarcomponent inside the modal only handles the bottom case (stickToBottomstyle) and doesn't account for side-positioned system bars in landscape (NavigationBar/index.android.tsx:19).Additionally, RN
<Modal>on Android creates a separate window, and there is noSafeAreaProviderinside the modal — the insets come from the app root's provider. This can causeuseSafeAreaInsets()to return incorrect left/right values inside the modal window in landscape, resulting in insufficient padding and the arrows being hidden behind the system navigation bar.What changes do you think we should make in order to solve the problem?
Two options (not mutually exclusive):
Add a
SafeAreaVieworSafeAreaProviderinside the modal to ensure correct insets are reported for the modal's own window context. This would makepaddingRight/paddingLeftfromgetModalPaddingStylesaccurate in landscape.Update the
NavigationBarcomponent (index.android.tsx) to handle landscape orientation — when the system nav bar is on the side, render the translucent background on the appropriate side (right or left) instead of always at the bottom.The first option is the more robust fix since it addresses the root issue (incorrect insets inside Modal), which would fix not just this calendar picker but any BOTTOM_DOCKED modal content in landscape.
What alternative solutions did you explore? (Optional)
mrn2negative margin from the calendar header arrow container would give slightly more breathing room, but doesn't address the fundamental safe area issue.Investigation details
Key code path:
DatePicker→DatePickerModal→PopoverWithMeasuredContentBOTTOM_DOCKEDModaldirectlyBaseModalrendersReanimatedModal(RN<Modal>withstatusBarTranslucent=true)width: '100%',overflow: 'hidden',paddingRightfromuseSafeAreaInsets()maxHeight: windowHeight * 0.75, content wrapped inScrollViewCalendarPickerheader arrows at right edge withmrn2negative marginIntroduced by: Expensify/App#85229 ("Unlock landscape mode") — merged 2026-04-07. This PR enabled landscape orientation on mobile devices, exposing this safe area handling gap in modals.
Next Steps for Contributor+ team: Reply with
@MelvinBot implement thisto create a draft PR,@MelvinBot <your feedback>to refine this analysis, or explain why you are rejecting Melvin's proposal.3 remaining items
GCyganek commentedon Apr 10, 2026
already fixed here
melvin-bot commentedon Apr 13, 2026
@rushatgabhane Eep! 4 days overdue now. Issues have feelings too...
melvin-bot commentedon Apr 15, 2026
@rushatgabhane Still overdue 6 days?! Let's take care of this!
melvin-bot commentedon Apr 17, 2026
@rushatgabhane Now this issue is 8 days overdue. Are you sure this should be a Daily? Feel free to change it!
GCyganek commentedon Apr 20, 2026
deployed to staging
mallenexpensify commentedon Apr 28, 2026
This is one of 4 issues linked in the below PR, if payment is due, it'll be handled here
truph01 commentedon Apr 29, 2026
We can close this one and handle the payment in the parent issue once all are done.