[Due for payment 2026-04-30] Profile - Zoom green dot slider is not fully visible and functioning in landscape.

[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: User Settings

Action Performed:

1. Launch app
2. Open profile - avatar
3. Turn to landscape
4. Tap upload phone - select a photo
5. Try to drag green dot
6. Turn to portrait and try to drag using zoom green dot scroller
7. Turn to landscape
8. Try to drag green dot

Expected Result:

Zoom green dot slider must be fully visible and functioning in landscape.

Actual Result:

Zoom green dot slider is not fully visible and functioning in landscape.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7124585_1775639013757.Screenrecorder-2026-04-08-14-26-53-404.mp4

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @mallenexpensify

[melvin-bot]

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

[melvin-bot]

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

[github-actions]

👋 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.

[melvin-bot]

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

[MelvinBot]

Proposal

What is the root cause of that problem?

In AvatarCropModal.tsx, the image crop area and the zoom slider share a vertical flex1 container (line 384-444). The image container size is calculated at line 90-96 as:

relativeHeight = max(height - CONTAINER_VERTICAL_MARGIN, INITIAL_SIZE)
imageContainerSize = min(relativeHeight, width)

CONTAINER_VERTICAL_MARGIN is only 40px (componentSizeNormal), which was designed to account for the rotate button height but does not account for the full slider row height (zoom icon + slider + rotate button + mt5 spacing ≈ 60px).

In landscape on Android, the available vertical space is severely reduced. The ImageCropView consumes nearly all of it (height minus only 40px), leaving insufficient room for the slider row below. The modal container has overflow: 'hidden' (ModalStyleUtils.ts:289), so the slider row is clipped. There is no ScrollView to allow scrolling to it.

This was exposed by PR #85229 ("Unlock landscape mode"), which enabled landscape orientation on Android where portrait was previously enforced.

What changes do you think we should make in order to solve the problem?

Increase CONTAINER_VERTICAL_MARGIN in src/CONST/index.ts (line 4553) to properly account for the full slider control row height — the zoom icon, slider, rotate button, and mt5 margin between the image and controls. A value around 70-80px (instead of the current 40px) should ensure the controls remain visible.

Additionally, in landscape mode the layout could benefit from capping the image container size more aggressively so the slider row always has enough room, regardless of screen dimensions. This could be done by adding a constant for the slider row height and subtracting it in initializeImageContainer instead of relying on a single margin constant.

What alternative solutions did you explore? (Optional)

1. Wrapping content in a ScrollView — would allow scrolling to the slider, but the crop gesture handling (pan/pinch) would conflict with scroll gestures, making the UX worse.
2. Side-by-side layout in landscape — placing the slider beside the image in landscape would be ideal UX but is a larger refactor and may be better suited as a follow-up enhancement.

---

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.

[JS00001]

@mjasikowski @GCyganek @truph01 could you look at this please