Revert "83598: Remove TestDrive from sign-up flow"#85140
Conversation
|
@chuckdries 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] |
Codecov Report❌ Looks like you've decreased code coverage for some files. Please write tests to increase, or at least maintain, the existing level of code coverage. See our documentation here for how to interpret this table.
|
Reviewer Checklist
Screenshots/VideosAndroid: HybridAppAndroid: mWeb ChromeiOS: HybridAppiOS: mWeb SafariMacOS: Chrome / Safari |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 94ffdf60b0
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
| return true; | ||
| } | ||
|
|
||
| if (action.type === 'RESET' && action.payload) { |
There was a problem hiding this comment.
Handle non-RESET actions in Test Drive modal detection
isNavigatingToTestDriveModal() only checks RESET payloads, but in-app Navigation.navigate(ROUTES.TEST_DRIVE_MODAL_ROOT.route) calls are dispatched as PUSH for static routes (see src/libs/Navigation/helpers/linkTo/index.ts, where NAVIGATE is rewritten to PUSH). In that common path, this guard will not recognize that the app is navigating to the modal, so the "dismissed modal" redirect logic is skipped and users can reopen a modal that should be blocked after dismissal.
Useful? React with 👍 / 👎.
| if (onboardingInitialPath.includes(ROUTES.TEST_DRIVE_MODAL_ROOT.route)) { | ||
| return `/${ROUTES.TEST_DRIVE_MODAL_ROOT.route}`; |
There was a problem hiding this comment.
Avoid matching demo routes as modal routes
The new includes() check treats any path containing onboarding/test-drive as the modal route, which also matches ROUTES.TEST_DRIVE_DEMO_ROOT (onboarding/test-drive/demo). When onboardingInitialPath is the demo URL, this now rewrites it to /onboarding/test-drive, so users resuming that path are sent to the modal instead of the demo.
Useful? React with 👍 / 👎.
|
🚧 @Valforte has triggered a test Expensify/App build. You can view the workflow run here. |
|
🧪🧪 Use the links below to test this adhoc build on Android, iOS, and Web. Happy testing! 🧪🧪
|
|
@Valforte please link the fixed issue in the future so we can better track blockers. I added it to the OP this time. |
Revert "83598: Remove TestDrive from sign-up flow" (cherry picked from commit 1787f76) (cherry-picked to staging by luacmartins)
|
🚀 Cherry-picked to staging by https://github.com/luacmartins in version: 9.3.37-1 🚀
|
|
🚀 Deployed to production by https://github.com/cristipaval in version: 9.3.37-10 🚀
|
|
🚀 Cherry-picked to staging by https://github.com/luacmartins in version: 9.3.38-0 🚀
|
Reverts #83750
Fixed issues
$ #85162
PR Author Checklist
### Fixed Issuessection aboveTestssectionOffline stepssectionQA stepssectiontoggleReportand notonIconClick)src/languages/*files and using the translation methodSTYLE.md) were followedAvatar, I verified the components usingAvatarare working as expected)StyleUtils.getBackgroundAndBorderStyle(theme.componentBG))npm run compress-svg)Avataris modified, I verified thatAvataris working as expected in all cases)Designlabel and/or tagged@Expensify/designso the design team can review the changes.ScrollViewcomponent to make it scrollable when more elements are added to the page.mainbranch was merged into this PR after a review, I tested again and verified the outcome was still expected according to theTeststeps.Screenshots/Videos
Android: Native
Android: mWeb Chrome
iOS: Native
iOS: mWeb Safari
MacOS: Chrome / Safari