[HOLD for payment 2024-02-14] [$500] Login - After opening public room and killing app user stuck on login page & back icon shown

[lanitochka17]

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: 1.4.31-4
Reproducible in staging?: Y
Reproducible in production?: Y
If this was caught during regression testing, add the test name, ID and link from TestRail: https://expensify.testrail.io/index.php?/tests/view/4228315
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: Applause - Internal Team
Slack conversation:

Action Performed:

1. Navigate to a public room via deeplink, e.g. https://staging.new.expensify.com/r/5408450846930023
2. Kill the app
3. Open the app again
4. Log in with any email address

Expected Result:

The back icon is no longer displayed and user is able to log in

Actual Result:

The back icon is displayed and it is not functioning. When user is trying to log in, user is stuck on the sign page with the "Incorrect magic code" message. After restarting the app, user is logged in

Workaround:

Unknown

Platforms:

Which of our officially supported platforms is this issue occurring on?

• Android: Native
• Android: mWeb Chrome
• iOS: Native
• iOS: mWeb Safari
• MacOS: Chrome / Safari
• MacOS: Desktop

Screenshots/Videos

Add any screenshot/video evidence

Bug6353889_1706134250494.video_2024-01-24_17-10-20.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~01434d068cd2fd6a96
• Upwork Job ID: 1750328972969820160
• Last Price Increase: 2024-01-25
• Automatic offers:
• jjcoffee | Reviewer | 28131302
• bernhardoj | Contributor | 28131303

[melvin-bot]

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

[melvin-bot]

Triggered auto assignment to @michaelhaxhiu (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.

[melvin-bot]

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

[lanitochka17]

We think that this bug might be related to #vip-vsp.
CC @quinthar

[bernhardoj]

Proposal

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

As anonymous user, closing and reopening the app will show a sign in page/modal, but the back button isn't functional.

What is the root cause of that problem?

When we open the app, openReportFromDeepLink will always be called, but with a null url, because we didn't do any deeplink. If we open it as an anonymous user, it will check whether the URL can be accessed by the user or not.

App/src/libs/actions/Report.ts

Lines 2068 to 2071 in 0d0b0a8

	if (Session.isAnonymousUser() && !Session.canAccessRouteByAnonymousUser(route)) {
	Session.signOutAndRedirectToSignIn(true);
	return;
	}

App/src/libs/actions/Session/index.ts

Lines 114 to 115 in 0d0b0a8

	if (shouldReplaceCurrentScreen) {
	Navigation.navigate(ROUTES.SIGN_IN_MODAL, CONST.NAVIGATION.TYPE.UP);

Because it's null, canAccessRouteByAnonymousUser will return false and will be redirected to the sign in page. Notice that we pass true to the param which will replace the current screen with the sign-in screen. So, the LHN is replaced with the sign-in page making it impossible to go back.

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

If the url (route) is empty, don't redirect to sign in page

if (route && Session.isAnonymousUser() && !Session.canAccessRouteByAnonymousUser(route)) {

UPDATE:
btw, I notice a similar issue with a different step. You won't be able to go back after pressing the "Sign in" button in the LHN header and that's because the press event object is passed to the function which will evaluate to true replacing the LHN.

App/src/pages/home/sidebar/SignInButton.js

Line 19 in 0d0b0a8

onPress={Session.signOutAndRedirectToSignIn}

we should update it like this () => Session.signOutAndRedirectToSignIn() to every occurrences

[dukenv0307]

Proposal

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

• Login - After opening public room and killing app user stuck on login page & back icon shown

What is the root cause of that problem?

• Generally, the RCA is that, we are considering the undefined route as the route that cannot be accessed by anonymous user. The detail is below.

• When we open the public room, Session.isAnonymousUser(): true

• Then kill app, reopen app, the below logic is called:
  

  App/src/libs/actions/Report.ts

  Lines 2068 to 2071 in 0d0b0a8

  	if (Session.isAnonymousUser() && !Session.canAccessRouteByAnonymousUser(route)) {
  	Session.signOutAndRedirectToSignIn(true);
  	return;
  	}

• Session.canAccessRouteByAnonymousUser(route) return false because in this case, route param is empty, that is not in routesCanAccessByAnonymousUser

• Because the signOutAndRedirectToSignIn is called with shouldReplaceCurrentScreen param is true, so it will replace the current screen (Home screen). Now, the screen stack just contains the RightModalNavigator, which leads to the back button and the "sign in" button is not functioning

• Note: The shouldReplaceCurrentScreen is to fix the bug:

the issue where you're able to go back from the sign in modal to the "protected route" (after being forced navigate to the sign in modal when trying to accessing the "protected route" directly. (see comment)

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

• We can update the routesCanAccessByAnonymousUser to:

    const routesCanAccessByAnonymousUser = [..., ROUTES.HOME];

because anonymous user can access the Home route.

• Then update:
  

  App/src/libs/actions/Session/index.ts

  Line 922 in 0d0b0a8

  const canAccessRouteByAnonymousUser = (route: string) => {

  
  to:

const canAccessRouteByAnonymousUser = (route: string = ROUTES.HOME) => {

• Also, we need to update routesCanAccessByAnonymousUser because it is outdated. There are many routes that can be accessed by anonymous user but we missed before, for example, desktop-signin-redirect, a/:accountID/avatar, r/:reportID/avatar, ...

What alternative solutions did you explore? (Optional)

• NA

[dukenv0307]

Update proposal`s solution