Fix - [CRITICAL] Multiple workspaces get created when someone either refreshes the page, or drops off and returns later.

[FitseTLT]

Details

Fixed Issues

$ https://github.com/Expensify/App/issues/52894 PROPOSAL: https://github.com/Expensify/App/issues/52894#issuecomment-2491045711

Tests

1. Sign-up on expensify.com
2. Choose the “1-9” option on the home page (signUpQualifier: vsb)
3. Get redirected to new.expensify.com
4. Observe a workspace is created
5. Don’t complete the onboarding modal steps (hasCompletedGuidedSetupFlow: false)
6. Refresh the page on web or close and re-open app on native
7. Verify that another workspace is not created

• [x] Verify that no errors appear in the JS console

Offline tests

Same as above

QA Steps

Same as above

• [x] Verify that no errors appear in the JS console

PR Author Checklist

• [x] I linked the correct issue in the ### Fixed Issues section above
• [x] I wrote clear testing steps that cover the changes made in this PR
  • [x] I added steps for local testing in the Tests section
  • [x] I added steps for the expected offline behavior in the Offline steps section
  • [x] I added steps for Staging and/or Production testing in the QA steps section
  • [x] I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
  • [x] 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)
  • [x] I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).
• [x] I included screenshots or videos for tests on all platforms
• [x] I ran the tests on all platforms & verified they passed on:
  • [x] Android: Native
  • [x] Android: mWeb Chrome
  • [x] iOS: Native
  • [x] iOS: mWeb Safari
  • [x] MacOS: Chrome / Safari
  • [x] MacOS: Desktop
• [x] I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
• [x] I followed proper code patterns (see Reviewing the code)
  • [x] 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)
  • [x] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
  • [x] I verified that comments were added to code that is not self explanatory
  • [x] 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.
  • [x] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
    • [x] If any non-english text was added/modified, I verified the translation was requested/reviewed in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:
  • [x] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
  • [x] 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 approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
  • [x] 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.
  • [x] I verified the JSDocs style guidelines (in STYLE.md) were followed
• [x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
• [x] I followed the guidelines as stated in the Review Guidelines
• [x] I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
• [x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
• [x] 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
• [x] I verified that if a function's arguments changed that all usages have also been updated correctly
• [x] If any new file was added I verified that:
  • [x] 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
• [x] If a new CSS style is added I verified that:
  • [x] A similar style doesn't already exist
  • [x] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(themeColors.componentBG))
• [x] 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.
• [x] 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)
• [x] 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.
• [x] 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.
• [x] If the PR modifies the form input styles:
  • [x] I verified that all the inputs inside a form are aligned with each other.
  • [x] I added Design label so the design team can review the changes.
• [x] 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.
• [x] 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.

Screenshots/Videos

Android: Native

https://github.com/user-attachments/assets/ef1b80af-ea7d-4ab3-99d8-9f2366601051

Android: mWeb Chrome

https://github.com/user-attachments/assets/9429dc86-34a4-4113-9e61-cc7938176a92

iOS: Native

https://github.com/user-attachments/assets/925c9ac7-14df-46df-9966-f4b6b1efea38

iOS: mWeb Safari

https://github.com/user-attachments/assets/bfe14ae0-60ef-4998-903c-84ab8bf1526a

MacOS: Chrome / Safari

https://github.com/user-attachments/assets/2794d79c-ab42-4ce5-963f-4062497594e1

MacOS: Desktop

https://github.com/user-attachments/assets/dfba3951-4c9c-4968-a22b-3c7dafde1628

[melvin-bot[bot]]

@jayeshmangwani 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]

[FitseTLT]

Working on uploading screenshots ...

[FitseTLT]

Upload finished

[jayeshmangwani]

Reviewer Checklist

• [x] I have verified the author checklist is complete (all boxes are checked off).
• [x] I verified the correct issue is linked in the ### Fixed Issues section above
• [x] I verified testing steps are clear and they cover the changes made in this PR
  • [x] I verified the steps for local testing are in the Tests section
  • [x] I verified the steps for Staging and/or Production testing are in the QA steps section
  • [x] 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)
  • [x] 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)
• [x] I checked that screenshots or videos are included for tests on all platforms
• [x] I included screenshots or videos for tests on all platforms
• [x] I verified tests pass on all platforms & I tested again on:
  • [x] Android: Native
  • [x] Android: mWeb Chrome
  • [x] iOS: Native
  • [x] iOS: mWeb Safari
  • [x] MacOS: Chrome / Safari
  • [x] MacOS: Desktop
• [x] 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
• [x] I verified proper code patterns were followed (see Reviewing the code)
  • [x] 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).
  • [x] I verified that comments were added to code that is not self explanatory
  • [x] 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.
  • [x] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
  • [x] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
  • [x] 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)
  • [x] 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.
  • [x] I verified the JSDocs style guidelines (in STYLE.md) were followed
• [x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
• [x] I verified that this PR follows the guidelines as stated in the Review Guidelines
• [x] 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)
• [x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
• [x] 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
• [x] If a new component is created I verified that:
  • [x] A similar component doesn't exist in the codebase
  • [x] All props are defined accurately and each prop has a /** comment above it */
  • [x] The file is named correctly
  • [x] The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
  • [x] The only data being stored in the state is data necessary for rendering and nothing else
  • [x] 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)
  • [x] 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)
  • [x] All JSX used for rendering exists in the render method
  • [x] 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
• [x] If any new file was added I verified that:
  • [x] 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
• [x] If a new CSS style is added I verified that:
  • [x] A similar style doesn't already exist
  • [x] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG)
• [x] 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.
• [x] 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)
• [x] 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.
• [x] 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.
• [x] 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:
  • [x] I verified that all the inputs inside a form are aligned with each other.
  • [x] I added Design label and/or tagged @Expensify/design so the design team can review the changes.
• [x] 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.
• [x] 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.
• [x] I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

Android: Native

Android: mWeb Chrome

https://github.com/user-attachments/assets/2fd67b3c-0e51-459c-9e17-6b1e325ec8c6

iOS: Native

https://github.com/user-attachments/assets/9b567a3f-517f-48f6-bf04-721313f1fb17

iOS: mWeb Safari

https://github.com/user-attachments/assets/40e39f43-ca75-4536-8371-6cd531959bc6

MacOS: Chrome / Safari

https://github.com/user-attachments/assets/ff74dd09-cf2d-4ab0-9b62-146b71aa5682

MacOS: Desktop

https://github.com/user-attachments/assets/921a3f5f-bf04-4c92-bc2e-e57f978de4b5

[jayeshmangwani]

@FitseTLT I'm not sure why, but on Android, a workspace is created twice if it comes from a closed app on onboarding flow.

https://github.com/user-attachments/assets/3ecbc133-2469-4cc0-a4ad-26580fb11eff

[FitseTLT]

I don't think so @jayeshmangwani Maybe you were on a wrong branch. I tried to exactly do what is on your video but couldn't reproduce

https://github.com/user-attachments/assets/39e377be-dffa-4307-b74b-6839b3df9660

[jayeshmangwani]

Maybe you were on a wrong branch

No, thats not the case, I am on right branch

[jayeshmangwani]

I am checking on real device, let's see if that my emulator thing

[jayeshmangwani]

For me, it's still creating two workspaces

[jayeshmangwani]

@mountiny Can we please generate build here so that we can test it on an Android device?"

[jayeshmangwani]

@FitseTLT Do you have any idea, How can we open the OD web link in the ND staging version of the app? We are testing locally using npx uri-scheme open, but how can we verify it on the staging version?

[FitseTLT]

@FitseTLT Do you have any idea, How can we open the OD web link in the ND staging version of the app? We are testing locally using npx uri-scheme open, but how can we verify it on the staging version?

@jayeshmangwani Sorry but I am totally not understanding what you meant.

[jayeshmangwani]

I am totally not understanding what you meant.

Sorry about that! Let me simplify it: how have you tested this PR on Android?

[FitseTLT]

npm run android

[jayeshmangwani]

Sorry, I didn’t quite get you. npm run android doesn’t work for me with this PR. Can you please at least show me on video how you trigger the Choose the “1-9” option on the home page (signUpQualifier: vsb) step on Android?

[github-actions[bot]]

🚧 @mountiny has triggered a test build. You can view the workflow run here.

[github-actions[bot]]

:test_tube::test_tube: Use the links below to test this adhoc build on Android, iOS, Desktop, and Web. Happy testing! :test_tube::test_tube:	Android :robot:	iOS :apple:
https://ad-hoc-expensify-cash.s3.amazonaws.com/android/52899/index.html	https://ad-hoc-expensify-cash.s3.amazonaws.com/ios/52899/index.html
Desktop :computer:	Web :spider_web:
https://ad-hoc-expensify-cash.s3.amazonaws.com/desktop/52899/NewExpensify.dmg	https://52899.pr-testing.expensify.com

---

:eyes: View the workflow run that generated this build :eyes:

[mountiny]

@jayeshmangwani here is the build

[jayeshmangwani]

Thanks, I’m checking it now

[jayeshmangwani]

@mountiny , I am trying to test the transition link from OldDot to NewDot on a native Android device for the signup flow when we select the VSB option on OD, but for me, it is always opening in mobile web. Is there any way you are aware of to test on a native Android device? Otherwise, this issue cannot be tested in a real scenario.

[mountiny]

I am not sure how to test the short-lived token in your dev setup, sorry 😬 its probably not possible as the deeplinks will be picked up in the actual app, not your dev apk

[jayeshmangwani]

I think we can proceed with this PR and merge it, as testing on both the production web and mobile app shows that we are not opening the transition deep link on mobile (when creating a new account and selecting the VSB option).

[OSBotify]

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