App: [PAID] [$500] Web - Signing show empty content when pressing go back from another tab.

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.3.90.1 Reproducible in staging?: y Reproducible in production?: y If this was caught during regression testing, add the test name, ID and link from TestRail: Email or phone of affected tester (no customers): Logs: https://stackoverflow.com/c/expensify/questions/4856 Expensify/Expensify Issue URL: Issue reported by: @hungvu193 Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1698145969463179

Action Performed:

Open 2 tabs
Try to sign in with expensifail account at the first tab.
At first tab, continue to choose Use magic code, after that press go back.
Now move to the second tab.
Notice that content of second tab is empty.

Expected Result:

Second tab should show the same content with the first tab.

Actual Result:

Content of the second tab is empty.

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

Android: Native

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

https://github.com/Expensify/App/assets/93399543/8346887f-5b30-419e-897e-18e0a792a959

https://github.com/Expensify/App/assets/93399543/6b3c7b44-59a9-4c03-90c3-750c4dc59ac8

MacOS: Desktop

View all open jobs on GitHub

Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~011276a45d6462ac66
Upwork Job ID: 1716875205299765248
Last Price Increase: 2023-11-14

Issue Owner

Current Issue Owner: @situchan

About this issue

Original URL
State: closed
Created 8 months ago
Comments: 38 (20 by maintainers)

Most upvoted comments

This is all wrapped up and paid out. Thanks again everyone!

strepanier03 on Dec 7, 2023

BZ Checklist: This came from Onyx. Not regression from app PR. As this is rare case, it’s not worthy of adding regression test. If disagrees, we can use QA Steps in PR as regression test step.

situchan on Dec 6, 2023

Awaiting proposal with correct root cause and solution

situchan on Oct 31, 2023

I would suggest using git bisect to try and locate the offending commit.

tgolen on Oct 30, 2023

Okay, we are able to repro this pretty easily but I do wonder if this is a limitation based on the comment from @wlegolas here. Although it does seem like the more recent proposals identify this as an Onyx issue so perhaps there is no limitation?

https://github.com/Expensify/App/assets/10925636/07dbc78d-082e-4284-a50a-82fc3d240a64

I’ll wait for @situchan to weigh in because they’re going to understand this much better than I do.

Thanks everyone!

strepanier03 on Oct 24, 2023