[$4000] Android - Infinite loading spinner appears when sign in to the app leaving idle for 10 min after sign out

[kavimuru]

If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!

---

Action Performed:

1. Launch the app

2. Log in with applausetester+0901abb@applause.expensifail.com

3. In LHN find the user applausetester+1226abb@applause.expensifail.com

4. Send Message to applausetester+1226abb@applause.expensifail.com

5. Go to Setting and log out

6. Leave the New Expensify app for about 10-15 minutes

7. Back again to New Expensify app and log in with applausetester+0901abb@applause.expensifail.com

Expected Result:

Log in with account

Actual Result:

Infinite loading when left app idle for 10 min after logout

Workaround:

Unknown

Platform:

Where is this issue occurring?

• Android

Version Number: 1.1.33.2
Reproducible in staging?: Yes
Reproducible in production?: No
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos:
Expensify/Expensify Issue URL:

Bug5424233_Screen_Recording_20220126-124622_New_Expensify.mp4

Issue reported by: Applause
Slack conversation:

View all open jobs on GitHub

[OSBotify]

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

Triggered auto assignment to @thienlnam (Engineering), see https://stackoverflow.com/c/expensify/questions/4319 for more details.

[thienlnam]

Looking into logs and recent issues that might have caused this, seeing a couple things in logs

https://staging.expensify.com/_devportal/tools/logSearch/#query=request_id:(%226d357ba62909ebe8-BOS%22)+AND+timestamp:[2022-01-25T23:04:17.301Z+TO+2022-01-26T01:04:17.301Z]&index=logs_expensify-015005

 User tried to get a policy they have no access to ~~ policyID: '_FAKE_'

Also considering it's loading spinner it seems like it is related to Onyx stuff
https://staging.expensify.com/_devportal/tools/logSearch/#query=request_id:(%226d357707afedebe8-DEN%22)+AND+timestamp:[2022-01-25T23:01:07.894Z+TO+2022-01-26T01:01:07.894Z]&index=logs_expensify-015005

[thienlnam]

Looks like this is most likely related - cc @luacmartins
#7397

[luacmartins]

It could be, but seems kind of odd. Have you been able to reproduce this on dev?

[thienlnam]

Agreed, I'm not able to get my android simulator working right now so unfortunately not. There have also been a couple Onyx updates that could be the problem but this one seemed most related to the sign in / sign out flow

[thienlnam]

@kavimuru Could you please try to reproduce this? I'm having issues with my dev and wanted to make sure it is happening consistently and is not a one-off

[thienlnam]

Looks like the only tester with Android 12 was able to reproduce this
https://expensify.slack.com/archives/C01GTK53T8Q/p1643242758028500?thread_ts=1643238659.022300&cid=C01GTK53T8Q

EDIT: Looks like it was also reproducible on A11 so it is not OS specific

[thienlnam]

Looking into logs on the account applausetester+0901abb@applause.expensifail.com -

From the video it looks like we aren't even getting to the splash screen so I've narrowed it down to a couple of areas
Slash screen status:

App/src/Expensify.js

Lines 163 to 176 in 45f5e38

	reportBootSplashStatus() {
	BootSplash
	.getVisibilityStatus()
	.then((status) => {
	const appState = AppState.currentState;
	Log.info('[BootSplash] splash screen status', false, {appState, status});
	if (status === 'visible') {
	const props = _.omit(this.props, ['children', 'session']);
	props.isAuthenticated = this.isAuthenticated();
	Log.alert('[BootSplash] splash screen is still visible', {props}, false);
	}
	});
	}

or some kind of error in the app init that causes us to hide the splash screen

App/src/components/ErrorBoundary/BaseErrorBoundary.js

Lines 38 to 43 in 45f5e38

	componentDidCatch(error, errorInfo) {
	this.props.logError(this.props.errorMessage, error, errorInfo);
	// We hide the splash screen since the error might happened during app init
	BootSplash.hide();
	}

[thienlnam]

The only issues on the checklist that we've merged that seems to possibly be related would be
Onyx updates cc @kidroca, any idea on this?
And this #7397 but that doesn't seem to make much sense