Expense - "Try it out" button reopens Create expense RHP and two tooltips appear

[jponikarchuk]

If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!

---

Version Number: 9.1.32-0
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: No, reproducible on hybrid only
If this was caught during regression testing, add the test name, ID and link from TestRail: Exp
Email or phone of affected tester (no customers): [email protected]
Issue reported by: Applause Internal Team
Device used: Mac 15.3 / Chrome
App Component: Money Requests

Action Performed:

1. Go to staging.new.expensify.com
2. Log in with a new Gmail account.
3. Create a new workspace.
4. Go to workspace chat.
5. Click + > Create expense.
6. Click Try it out on the tooltip.
7. Click Try it out on the tooltip again.

Expected Result:

In Step 6, after clicking Try it out button on the tooltip for the first time, app will proceed to the confirmation page.

Actual Result:

In Step 6, after clicking Try it out button on the tooltip for the first time, app reopens Create expense RHP.
In Step 7, after clicking Try it out button on the tooltip for the second time, two tooltips appear.

Workaround:

Unknown

Platforms:

• Android: Standalone
• Android: HybridApp
• Android: mWeb Chrome
• iOS: Standalone
• iOS: HybridApp
• iOS: mWeb Safari
• MacOS: Chrome / Safari
• MacOS: Desktop

Screenshots/Videos

1.mp4

View all open jobs on GitHub

[melvin-bot]

Triggered auto assignment to @laurenreidexpensify (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.

[melvin-bot]

Triggered auto assignment to @amyevans (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.

[amyevans]

I believe this is coming from #60479. @nkdengineer @DylanDylann @grgia could you take a look please?

[nkdengineer]

Created a fix here #60777. The problem is IOURequestStartPage change the reportID to the previous reportID again here after we changed this

App/src/pages/iou/request/IOURequestStartPage.tsx

Lines 73 to 77 in a857e00

	useFocusEffect(
	useCallback(() => {
	if (transaction?.reportID === reportID || isLoadingSelectedTab) {
	return;
	}

Then the flow is reset because this condition is incorrect.

App/src/pages/iou/request/step/IOURequestStepConfirmation.tsx

Line 221 in a857e00

const isCurrentReportID = transaction?.isFromGlobalCreate

The solution is we will change the isFromGlobalCreate to true then we can compare with the correct reportID here

cc @DylanDylann @grgia

[nkdengineer]

The PR is ready.

[amyevans]

Thanks!

[amyevans]

We CP'ed the PR, and I requested a retest here: https://expensify.slack.com/archives/C9YU7BX5M/p1745609411393339

[amyevans]

@nkdengineer QA retested and said on a Samsung Galaxy s10/ Android 12 the tooltip is not responsive:

Screen_Recording_20250425_230108_Expensify.mp4

[nkdengineer]

@amyevans It looks like this is a known bug with SamSung devices that onPress is never triggered. I created a draft with the same solution. Please help to trigger a build and ask QA to retest again with this device.

App/src/components/ProductTrainingContext/index.tsx

Lines 265 to 277 in a9b6d36

	// On some Samsung devices, `onPress` is never triggered.
	// So, we use `onPressIn` for Android to ensure the button is pressable.
	onPressIn={
	getPlatform() === CONST.PLATFORM.ANDROID
	? () => {
	hideTooltip(true);
	}
	: undefined
	}
	// For other platforms, we stick with `onPress`.
	onPress={
	getPlatform() !== CONST.PLATFORM.ANDROID
	? () => {

[amyevans]

#60936 (comment) - looks like it's still reproducible unfortunately

[laurenreidexpensify]

@nkdengineer @DylanDylann @amyevans what's the latest here?

[nkdengineer]

I believe the original bug was fixed, we're good to close

[amyevans]

Yeah we're all set here, thank you!