[Due for payment 2025-08-20] [$250] Onboarding - Tapping back button in work email page show inconsistent behavior in mweb & android

[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: v9.1.53-1
Reproducible in staging?: Yes
Reproducible in production?: Yes
If this was caught during regression testing, add the test name, ID and link from TestRail: N/a
Email or phone of affected tester (no customers): slottwo1newiop@gmail.com
Issue reported by: Applause Internal Team
Device used: Redminote 10s android 13
App Component: Other

Action Performed:

1. Launch app in both mweb and android
2. Enter a new gmail account
3. Tap continue
4. Tap join
5. Tap device back button in what's your work email page

Expected Result:

Tapping device back button in what's your work email page must show same behaviour in mweb and android.

Actual Result:

Tapping device back button in what's your work email page shows error "please finish the set up questions to start before using the app" message in mweb but in android no error message.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

1.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~021929530258746301982
• Upwork Job ID: 1929530258746301982
• Last Price Increase: 2025-07-21
• Automatic offers:
• nyomanjyotisa | Contributor | 108315135

Issue Owner

Current Issue Owner: @muttmuure

[melvin-bot]

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

[nyomanjyotisa]

Proposal

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

Onboarding - Tapping back button in work email page show inconsistent behavior in mweb & android

What is the root cause of that problem?

The root cause is in the Android native implementation of the OnboardingWorkEmail page. Here the BackHandler is set up to block the hardware back button by returning true, but it doesn't show any error message to the user

App/src/pages/OnboardingWorkEmail/index.native.tsx

Line 12 in 352de72

const backAction = () => true;

In contrast, the mobile web version uses the OnboardingWrapper component which relies on the navigation router logic that properly shows the error message

App/src/libs/Navigation/AppNavigator/createRootStackNavigator/RootStackRouter.ts

Lines 45 to 49 in 352de72

	// We want to prevent the user from navigating back to a non-onboarding screen if they are currently on an onboarding screen
	if (isOnboardingFlowName(currentFocusedRoute?.name) && !isOnboardingFlowName(targetFocusedRoute?.name)) {
	Welcome.setOnboardingErrorMessage(Localize.translateLocal('onboarding.purpose.errorBackButton'));
	return true;
	}

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

We should modify the Android native implementation to show the same error message when the back button is pressed

App/src/pages/OnboardingWorkEmail/index.native.tsx

Line 12 in 352de72

const backAction = () => true;

            const backAction = () => {
                setOnboardingErrorMessage(translateLocal('onboarding.purpose.errorBackButton'));
                return true;
            };

What specific scenarios should we cover in automated tests to prevent reintroducing this issue in the future?

N/A


What alternative solutions did you explore? (Optional)

[melvin-bot]

@muttmuure Eep! 4 days overdue now. Issues have feelings too...

[melvin-bot]

Job added to Upwork: https://www.upwork.com/jobs/~021929530258746301982

[melvin-bot]

Triggered auto assignment to Contributor-plus team member for initial proposal review - @jayeshmangwani (External)

[muttmuure]

Awaiting C+ review