[HOLD #87170]Create - No "Try it out" toolpit displayed while creating first scan expense.

[jponikarchuk]

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.61-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: #82255
Email or phone of affected tester (no customers): ibellicotest+2250@gmail.com
Issue reported by: Applause Internal Team
Bug source: Pull Request QA execution
Device used: Windows 11 / Chrome
App Component: Money Requests

Action Performed:

1. Open the staging.new.expensify.com website.
2. Sign up with a new account.
3. Complete onboarding modal selecting "Track and budget expenses" option.
4. Click on FAB > "Create Expense"
5. When landing on "Scan" tab, note that there is no "Try it out" toolpit encouraging to try scanning first receipt.

Expected Result:

When user starts the "Create Expense" flow for the first time, a "Try iy out" toolpit should appear on "Scan" tab, encouraging the user to scan first receipt.

Actual Result:

When user starts the "Create Expense" flow for the first time and lands on "Scan" tab, no "Try it out" tooplit is visible.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Video.mp4

View all open jobs on GitHub

[melvin-bot]

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

[melvin-bot]

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

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

Issue Analysis

Root Cause: The "Try it out" tooltip on the Scan tab is gated behind the NEWDOT_MANAGER_MCTEST beta flag (newDotManagerMcTest). If the tester's account does not have this beta enabled, the tooltip will never appear regardless of other conditions.

Recommended Fix: Verify whether the NEWDOT_MANAGER_MCTEST beta is intentionally required. If this tooltip should appear for all new users (not just beta users), remove the isBetaEnabled(CONST.BETAS.NEWDOT_MANAGER_MCTEST) condition from the shouldShow parameter in IOURequestStartPage.tsx:272.

Investigation details

The tooltip is implemented at src/pages/iou/request/IOURequestStartPage.tsx:269-286 and configured in src/components/ProductTrainingContext/TOOLTIPS.ts:62-69. All of the following conditions must be true for it to display:

1. NEWDOT_MANAGER_MCTEST beta is enabled for the user
2. User hasn't previously dismissed the tooltip or submitted an expense (NVP_DISMISSED_PRODUCT_TRAINING.scanTestTooltip)
3. Scan tab is the active tab
4. User is not offline on web
5. User is not in a paid policy
6. User is not in the nudge migration
7. Onboarding is completed
8. App is fully loaded
9. No higher-priority tooltip is active (this tooltip has priority 900, lower than most others)

The most likely cause is condition #1 — the beta flag. A new staging account created during testing would only have this beta if it's been rolled out to staging. Other possible blockers are condition #5 (paid policy) or condition #9 (another tooltip with higher priority taking precedence).

Note: There is a related open issue to remove this tooltip entirely: #87170 ("Remove SCAN_TEST_TOOLTIP from Create Expense Scan flow"). If that removal is the intended direction, this bug may be moot.

---

Next Steps: Reply with @MelvinBot implement this to create a draft PR, or @MelvinBot <your feedback> to refine this analysis.