(2nd) Fix long loading from public and redirect to last accessed report by wildan-m · Pull Request #50629 · Expensify/App

wildan-m · 2024-10-11T08:46:55Z

Details

Fix Sign in long loading when navigating via public room link and logging in as a new account.

Reported regressions:
#50549 can't replicated even when my PR applied
#50560 will need separate investigation because that issue related to withOnyx migration and not directly related to the main logic in this PR #50560 (comment)

Fixed Issues

$ #48715
$ #50578
PROPOSAL: #48715 (comment)

Tests

Open app
Log out
Go to to this link / report https://staging.new.expensify.com/r/7075912447943023
Tap sign in
Enter credentials and log in as a new Gmail account
Select any option (e.g. something else)
Tap continue
Verify that the loading has finished and is not frozen.
Verify user redirection to the opened report from the 3rd step.
[x] Verify that no errors appear in the JS console

Offline tests

Same as test

QA Steps

Same as test

Verify that no errors appear in the JS console

PR Author Checklist

Screenshots/Videos

Android: Native

Kapture.2024-10-12.at.11.25.46.mp4

Android: mWeb Chrome

Kapture.2024-10-12.at.11.29.45.mp4

iOS: Native

Kapture.2024-10-12.at.11.21.55.mp4

iOS: mWeb Safari

Kapture.2024-10-12.at.11.34.27.mp4

MacOS: Chrome / Safari

Kapture.2024-10-12.at.11.17.09.mp4

MacOS: Desktop

Kapture.2024-10-12.at.11.12.11.mp4

…rom deeplinking

…x/48715-long-loading-2nd-attempt

… logic

… report

melvin-bot · 2024-10-12T05:34:20Z

@thesahindia Please copy/paste the Reviewer Checklist from here into a new comment on this PR and complete it. If you have the K2 extension, you can simply click: [this button]

thesahindia · 2024-10-15T16:19:55Z

Reviewer Checklist

I have verified the author checklist is complete (all boxes are checked off).
I verified the correct issue is linked in the ### Fixed Issues section above
I verified testing steps are clear and they cover the changes made in this PR
- I verified the steps for local testing are in the Tests section
- I verified the steps for Staging and/or Production testing are in the QA steps section
- I verified the steps cover any possible failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
- I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
I checked that screenshots or videos are included for tests on all platforms
I included screenshots or videos for tests on all platforms
I verified tests pass on all platforms & I tested again on:
- Android: Native
- Android: mWeb Chrome
- iOS: Native
- iOS: mWeb Safari
- MacOS: Chrome / Safari
- MacOS: Desktop
If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
I verified proper code patterns were followed (see Reviewing the code)
- I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick).
- I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
- I verified that comments were added to code that is not self explanatory
- I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
- I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
- I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
- I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
- I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
- I verified the JSDocs style guidelines (in STYLE.md) were followed
If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
I verified that this PR follows the guidelines as stated in the Review Guidelines
I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
If a new component is created I verified that:
- A similar component doesn't exist in the codebase
- All props are defined accurately and each prop has a /** comment above it */
- The file is named correctly
- The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
- The only data being stored in the state is data necessary for rendering and nothing else
- For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
- Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
- All JSX used for rendering exists in the render method
- The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions
If any new file was added I verified that:
- The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory
If a new CSS style is added I verified that:
- A similar style doesn't already exist
- The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG)
If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:
- I verified that all the inputs inside a form are aligned with each other.
- I added Design label and/or tagged @Expensify/design so the design team can review the changes.
If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

Android: Native

Screen.Recording.2024-10-08.at.11.31.39.PM.mov

Android: mWeb Chrome

Screen.Recording.2024-10-08.at.11.10.12.PM.mov

iOS: Native

Screen.Recording.2024-10-08.at.11.58.50.PM.mov

iOS: mWeb Safari

Screen.Recording.2024-10-09.at.12.01.50.AM.mov

MacOS: Chrome / Safari

Screen.Recording.2024-10-08.at.10.16.18.PM.mov

MacOS: Desktop

Screen.Recording.2024-10-08.at.10.40.23.PM.mov

thesahindia

Tests well!

OSBotify · 2024-10-16T06:16:36Z

✋ This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

github-actions · 2024-10-17T01:59:53Z

🚀 Deployed to staging by https://github.com/lakchote in version: 9.0.50-0 🚀

platform	result
🤖 android 🤖	success ✅
🖥 desktop 🖥	success ✅
🍎 iOS 🍎	success ✅
🕸 web 🕸	success ✅

github-actions · 2024-10-18T18:48:43Z

🚀 Deployed to production by https://github.com/marcaaron in version: 9.0.50-8 🚀

platform	result
🤖 android 🤖	success ✅
🖥 desktop 🖥	success ✅
🍎 iOS 🍎	success ✅
🕸 web 🕸	success ✅

ahmedGaber93 · 2025-11-16T02:29:24Z

+    activeWorkspaceID?: string,
+    backTo?: string,
+) => {
+    Navigation.dismissModal();


Coming from #73365, moving Navigation.dismissModal(); inside navigateAfterOnboarding cause this Console Warn. For more details #73365 (comment)

wildan-m added 3 commits October 11, 2024 09:44

WIP: Fix regression long loading

f49e078

Revert AuthScreens withOnyx migration, it cause re-login in desktop f…

e9d9e26

…rom deeplinking

prettier, lint

8db66d3

wildan-m mentioned this pull request Oct 11, 2024

[HOLD for payment 2024-10-25] [HOLD for payment 2024-10-17] [$250] Sign in - Account settings long loading if navigate via public room link & login as new account #48715

Closed

6 tasks

wildan-m added 3 commits October 12, 2024 08:03

Merge branch 'main' of https://github.com/wildan-m/App into wildan/fi…

28cf470

…x/48715-long-loading-2nd-attempt

Fix navigation after onboarding, apply to accounting, extract similar…

237769e

… logic

Keep previous navigation logic if we can't find desired last accessed…

61bca5f

… report

wildan-m marked this pull request as ready for review October 12, 2024 05:34

wildan-m requested a review from a team as a code owner October 12, 2024 05:34

melvin-bot Bot requested review from thesahindia and removed request for a team October 12, 2024 05:34

thesahindia approved these changes Oct 15, 2024

View reviewed changes

melvin-bot Bot requested a review from lakchote October 15, 2024 16:20

lakchote approved these changes Oct 16, 2024

View reviewed changes

lakchote merged commit 927b40d into Expensify:main Oct 16, 2024

github-actions Bot mentioned this pull request Oct 17, 2024

Deploy Checklist: New Expensify 2024-10-17 #50969

Closed

90 tasks

IuliiaHerets mentioned this pull request Oct 18, 2024

[$125] Hybrid App - Deeplinking opens mWeb or NewDot stg app but not the Hybrid app #51090

Closed

8 tasks

melvin-bot Bot mentioned this pull request Oct 18, 2024

[HOLD for payment 2024-10-25] [$250] Onboarding - New user lands on workspace chat when 'Manage my team's expenses' selected in modal #50578

Closed

6 tasks

ahmedGaber93 reviewed Nov 16, 2025

View reviewed changes

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

(2nd) Fix long loading from public and redirect to last accessed report#50629

(2nd) Fix long loading from public and redirect to last accessed report#50629
lakchote merged 6 commits into
Expensify:mainfrom
wildan-m:wildan/fix/48715-long-loading-2nd-attempt

wildan-m commented Oct 11, 2024 •

edited

Loading

Uh oh!

melvin-bot Bot commented Oct 12, 2024

Uh oh!

thesahindia commented Oct 15, 2024

Uh oh!

thesahindia left a comment

Uh oh!

OSBotify commented Oct 16, 2024

Uh oh!

github-actions Bot commented Oct 17, 2024

Uh oh!

github-actions Bot commented Oct 18, 2024

Uh oh!

ahmedGaber93 Nov 16, 2025

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

5 participants

Conversation

wildan-m commented Oct 11, 2024 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Details

Fixed Issues

Tests

Offline tests

QA Steps

PR Author Checklist

Screenshots/Videos

Uh oh!

melvin-bot Bot commented Oct 12, 2024

Uh oh!

thesahindia commented Oct 15, 2024

Reviewer Checklist

Screenshots/Videos

Uh oh!

thesahindia left a comment

Choose a reason for hiding this comment

Uh oh!

OSBotify commented Oct 16, 2024

Uh oh!

github-actions Bot commented Oct 17, 2024

Uh oh!

github-actions Bot commented Oct 18, 2024

Uh oh!

ahmedGaber93 Nov 16, 2025

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

5 participants

wildan-m commented Oct 11, 2024 •

edited

Loading