Distance - Rate change tooltip does not reappear after user stops scrolling

[applause-bot]

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: 9.4.7-3
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: #93103
Email or phone of affected tester (no customers): applausetester+ssndjois2jd1@applause.expensifail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: iPhone 15 Pro Max / iOS 26.5
App Component: Workspace Settings

Action Performed:

Precondition:

• Log in with Expensifail account.
• Enable Distance rates.
• Create the following distance rates:
  Rate A: $0.67/mi, valid Jan 1 2025 - Dec 31 2025
  Rate B: $0.70/mi, valid Jan 1 2026 - Dec 31 2026

1. Launch Expensify app.
2. Go to workspace chat.
3. Tap + > Track distance > Manual.
4. Enter amount > Next.
5. Tap Date and select date to 2025.
6. Save the date.
7. On confirm page, after tooltip appears, scroll up.

Expected Result:

Tooltip will reappear after user stops scrolling (similar to web).

Actual Result:

Tooltip does not reappear after user stops scrolling.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

To be added by Applause Leads

View all open jobs on GitHub

Bug7181365_1781539653480.ScreenRecording_06-16-2026_00-05-10_1.mp4

Applause Internal Information
Exported by: Iuliia Herets
Bug ID: 7181365

[applause-bot]

While Applause doesn't embed attachments for this bug, here are the links for quick view:
https://platform.applause.com/services/links/v1/external/16c48d3352c57ae487fb3930d8b1c73b4def39f313c33659cbc070cb41bd68ec

[melvin-bot]

You have been assigned to this deploy blocker because you recently merged this PR: #93103

[melvin-bot]

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

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

[MelvinBot]

Proposal

Please re-state the problem that we are trying to solve in this issue.

On the distance request confirmation page (native iOS/Android), the "We updated the rate based on your travel date" educational tooltip on the Rate field hides while scrolling but does not reappear after the user stops scrolling. On web it reappears as expected.

What is the root cause of that problem?

The hide/reappear-on-scroll logic lives in BaseEducationalTooltip.tsx. On scroll-stop it calls renderTooltip(), which re-measures the anchor and runs a bounds-visibility check (BaseEducationalTooltip.tsx:45-66) to decide whether to showTooltip() or hideTooltip().

That check subtracts hard-coded chrome offsets that don't match the confirmation screen's layout:

• availableHeightForBottom = dimensions.height - (bottom + variables.bottomTabHeight - offset) — line 55

The Rate field is rendered in the list footer (RateField.tsx), which naturally sits near the bottom of the scroll content. The confirmation page is an RHP with no bottom tab, yet variables.bottomTabHeight (72px) is unconditionally subtracted. The only platform-divergent code in this path is the measurement primitive — native uses measure()→pageY (index.android.ts) while web uses measureInWindow() (index.ts) against a full-screen window. On native this makes availableHeightForBottom < 0, so renderTooltip() takes the hideTooltip() branch (line 63) instead of showTooltip().

The scroll-end event itself fires correctly (useScrollEventEmitter emits SCROLLING(false) 250ms after the last scroll — confirmed working for the LHN tooltip which uses the identical pattern), so the failure is purely in the visibility math, not the event plumbing.

Investigation details & confidence

• Reappear is driven by DeviceEventEmitter CONST.EVENTS.SCROLLING, emitted by useScrollEventEmitter.ts and wired into the confirmation list's FlashList onScroll at BaseSelectionListWithSections.tsx:448-451.
• The same hide/reappear pattern works for the LHN product-training tooltip (LHNOptionsList.tsx) on native, which rules out the event emitter and confirms the anchor ref is populated.
• Confidence: Medium. The bounds check is the only platform-divergent branch in the reappear path, but I could not compute the exact native pageY for the footer without on-device instrumentation. To confirm, add a temporary log at line 62 printing {y, height, dimensions.height, insets, availableHeightForBottom} and reproduce on iOS/Android — expect availableHeightForBottom < 0 while the field is visible.

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

In the renderTooltip() bounds check in BaseEducationalTooltip.tsx:45-66, stop subtracting the hard-coded variables.bottomTabHeight / variables.contentHeaderHeight chrome offsets when the screen has no bottom tab / NewDot header (the RHP confirmation case). The visibility test should compare the measured anchor rect against the actual scroll-container bounds (or window + safe-area insets only), rather than against Dimensions.get('window') minus magic constants — so a footer field that is genuinely on-screen evaluates as visible and showTooltip() runs after scroll-stop.

What alternative solutions did you explore?

• Since this is a DeployBlockerCash on a brand-new feature (PR feat: update confirmation and rate selection UX for date-aware mileage rates #93103) and the regression is a cosmetic tooltip-reappear edge case (the tooltip still shows initially, still hides on scroll, and the core date-aware rate behavior is unaffected), one option is to downgrade off the deploy blocker and fix forward rather than revert the whole feature PR.
• Alternatively, plumb a shouldHideOnScroll consumer that recomputes visibility against the FlashList's measured viewport instead of the global window.

---

Next Steps for Contributor+ team:
To accept: @MelvinBot implement [this](https://github.com/Expensify/App/issues/93603) to create a draft PR.
To refine: @MelvinBot <your feedback>
To reject: Explain why you are rejecting Melvin's proposal.

[rlinoz]

cc: @Krishna2323