[$250] Android Hybrid - Login - White screen when backgrounding app after entering magic code

[vincdargento]

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.0.69-2
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: No
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): [email protected]
Issue reported by: Applause Internal Team

Action Performed:

1. Open the Expensify app.
2. Tap on "Continue With Email"
3. Enter valid credentials.
4. Tap on "Next" and wait until receiving the magic code.
5. Enter the received magic code and tap on "Log In"
6. While the app is loading, background it.
7. Wait a few seconds and reopen it.
8. Verify that the login process was successful and you land on inbox.

Expected Result:

The user should be correctly logged in, despite backgrounding the app during the login process.

Actual Result:

A white screen is displayed when backgrounding the app for a few seconds while loading after entering the received Magic Code. The user has to kill the app and relaunch it to enter the account after this.

Workaround:

Unknown

Platforms:

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

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

Screenshots/Videos

bug.mp4

log.txt

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~021863674659316493760
• Upwork Job ID: 1863674659316493760
• Last Price Increase: 2024-12-02
• Automatic offers:
• ikevin127 | Reviewer | 105172764

Issue Owner

Current Issue Owner: @ikevin127

[melvin-bot]

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

[vincdargento]

@stitesExpensify FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors.

[melvin-bot]

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

[melvin-bot]

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

[ikevin127]

@stitesExpensify This is Android: HybridApp therefore should be Internal as External contributors don't have access to the HybridApp repo.

[stitesExpensify]

ah thanks @ikevin127 I wasn't aware that hybrid app issues were specific to that repo and couldn't be caused by the regular /app repo

[ikevin127]

Sure, usually when Android: Standalone or Android: mWeb Chrome are not checked in the Platforms section and when the issue's title states Android Hybrid we assume this is specific to Android: HybridApp.

[mountiny]

Assigning myself too as its most likely coming from the native-stack PR that I have pushed ahead. SWM will have a look into this tomorrow

[mateuuszzzzz]

Hi, I'm going to investigate this issue

[melvin-bot]

📣 @ikevin127 🎉 An offer has been automatically sent to your Upwork account for the Reviewer role 🎉 Thanks for contributing to the Expensify app!

Offer link
Upwork job

[mateuuszzzzz]

Update: I haven't found anything that could lead to recent changes in codebase. I'm continuing investigation

EDIT: It seems like this issue happens only if we want to open NewDot after successful sign-in. I think we might have an issue with ReactNativeActivity start. Perhaps it's not possible to start this activity when app is in background

[mateuuszzzzz]

I confirmed that Android blocks activity start, because app is in background. I'm looking for a fix

[mountiny]

Nice, great digging!

[mateuuszzzzz]

I managed to find a fix, and I'm preparing a PR so that anyone can verify it. I would also like to test the transition between OD and ND, as well as different scenarios where the app is opened from the background.