[Due for payment 2026-04-16] [Due for payment 2026-04-14] Android - Scan - App crashes when interacting with scan tooltip

[mitarachim]

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.3.53-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: #86541
Email or phone of affected tester (no customers): jsdjosidjiojisojio3@gmail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Samsung Galaxy S25 FE / Android 16
App Component: Money Requests

Action Performed:

1. Launch Expensify app.
2. Log in with a new Gmail account.
3. Open FAB > Create expense > Scan.
4. Tap Try it out button on the tooltip.

Expected Result:

App will not crash.

Actual Result:

App crashes when interacting with scan tooltip.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7123264_1775527233415.az-recorder-20260407-095736_aBPNtFRC.mp4

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @mallenexpensify

[melvin-bot]

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

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

[OSBotify]

Investigation Summary: Frontend bug. Causing PR: #86541 (No QA Add IDs to tooltips for tracking by @nkdengineer, High confidence). Recommendation: REVERT. PR 86541 introduced two Firebase Analytics event names that exceed the 40-character limit enforced by @react-native-firebase/analytics - prod_training_scan_test_tooltip_dismissed (41 chars) and prod_training_scan_test_tooltip_confirmed (41 chars). The logEvent call at node_modules/@react-native-firebase/analytics/lib/index.js line 102 throws an uncaught Error when name.length > 40, crashing the app on Android. The native GTM wrapper at src/libs/GoogleTagManager/index.native.ts has no try/catch around this call. Labels: Keeping DeployBlockerCash (App PR caused this). Removing DeployBlocker since fix is needed in the App repo only.