Skip to content

Expense - Side arrow to navigate to next month is hidden behind navigation bar. #87374

Closed

Description

@lanitochka17

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:

  1. Launch app
  2. Open an expense
  3. Tap date
  4. Turn to landscape
  5. 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

View all open jobs on GitHub

Issue OwnerCurrent Issue Owner: @rushatgabhane

Activity

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

    @melvin-bot

    @mjasikowski recently merged #85229, but they are OOO right now, so I'll auto-assign someone else.

  3. melvin-bot commented on Apr 8, 2026

    @melvin-bot

    Triggered auto assignment to @deetergp (DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.

  4. melvin-bot commented on Apr 8, 2026

    @melvin-bot

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

  5. github-actions commented on Apr 8, 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.
  6. MelvinBot commented on Apr 8, 2026

    @MelvinBot
    Contributor

    Proposal

    What is the root cause of that problem?

    The date picker opens as a BOTTOM_DOCKED modal on native (PopoverWithMeasuredContent/index.tsx:34). In landscape on Android, the modal container has width: '100%' and overflow: 'hidden' (ModalStyleUtils.ts:230-234), which refers to the full-screen window (including behind system bars, since statusBarTranslucent is enabled).

    The calendar header's month navigation arrows are positioned with justifyContentEnd and mrn2 (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 getModalPaddingStyles applies paddingRight from safe area insets (styles/utils/index.ts:654), the NavigationBar component inside the modal only handles the bottom case (stickToBottom style) 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 no SafeAreaProvider inside the modal — the insets come from the app root's provider. This can cause useSafeAreaInsets() 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):

    1. Add a SafeAreaView or SafeAreaProvider inside the modal to ensure correct insets are reported for the modal's own window context. This would make paddingRight/paddingLeft from getModalPaddingStyles accurate in landscape.

    2. Update the NavigationBar component (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)

    • Removing the mrn2 negative margin from the calendar header arrow container would give slightly more breathing room, but doesn't address the fundamental safe area issue.
    • Adding hardcoded landscape padding to the calendar picker would be a narrow workaround that doesn't fix other modals.
    Investigation details

    Key code path:

    1. User taps date → DatePicker → DatePickerModal → PopoverWithMeasuredContent
    2. On native, this returns a BOTTOM_DOCKED Modal directly
    3. BaseModal renders ReanimatedModal (RN <Modal> with statusBarTranslucent=true)
    4. Modal container: width: '100%', overflow: 'hidden', paddingRight from useSafeAreaInsets()
    5. In landscape: maxHeight: windowHeight * 0.75, content wrapped in ScrollView
    6. CalendarPicker header arrows at right edge with mrn2 negative margin

    Introduced 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 this to create a draft PR, @MelvinBot <your feedback> to refine this analysis, or explain why you are rejecting Melvin's proposal.

  7. 3 remaining items

  8. added and removed
    DeployBlockerCashThis issue or pull request should block deployment
    on Apr 8, 2026
  9. GCyganek commented on Apr 10, 2026

    @GCyganek
    Contributor

    already fixed here

  10. melvin-bot commented on Apr 13, 2026

    @melvin-bot

    @rushatgabhane Eep! 4 days overdue now. Issues have feelings too...

  11. melvin-bot commented on Apr 15, 2026

    @melvin-bot

    @rushatgabhane Still overdue 6 days?! Let's take care of this!

  12. melvin-bot commented on Apr 17, 2026

    @melvin-bot

    @rushatgabhane Now this issue is 8 days overdue. Are you sure this should be a Daily? Feel free to change it!

  13. GCyganek commented on Apr 20, 2026

    @GCyganek
    Contributor

    deployed to staging

  14. mallenexpensify commented on Apr 28, 2026

    @mallenexpensify
    Contributor

    This is one of 4 issues linked in the below PR, if payment is due, it'll be handled here

  15. truph01 commented on Apr 29, 2026

    @truph01
    Contributor

    We can close this one and handle the payment in the parent issue once all are done.

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