-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
chore(runway): cherry-pick fix: cp-7.50.0 fix infinite loader and inconsistent completedOnboarding
value
#16726
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore(runway): cherry-pick fix: cp-7.50.0 fix infinite loader and inconsistent completedOnboarding
value
#16726
Conversation
…onsistent `completedOnboarding` value (#16695) ## **Description** This PR removes the backfill for `completedOnboarding` that was located in `app/store/index.ts` and introduces a new `useCompletedOnboardingEffect` that observes `KeyringControllerState.vault` and the current value of `completedOnboarding` in order to automatically set `completedOnboarding`. This ensures that `completedOnboarding` is rightfully set, even when the user kills the app right before completing onboarding, or during the reset wallet flow. ## **Related issues** Fixes: #16638 Related to: https://consensyssoftware.atlassian.net/browse/IDENTITY-152 ## **Manual testing steps** 1. Onboard as a new user 2. Reset your wallet 3. Kill the app 4. Reload the app 5. Verify that there's no infinite loader 6. Onboard as a new user BUT kill the app just before clicking "Done" (the last onboarding step) 7. Reload the app and login 8. Verify that `completedOnboarding` is true, either by verifying the state logs, or by verifying that account syncing was dispatched ## **Screenshots/Recordings** <!-- If applicable, add screenshots and/or recordings to visualize the before and after of your change. --> ### **Before** <!-- [screenshots/recordings] --> ### **After** <!-- [screenshots/recordings] --> ## **Pre-merge author checklist** - [x] I’ve followed [MetaMask Contributor Docs](https://github.com/MetaMask/contributor-docs) and [MetaMask Mobile Coding Standards](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/CODING_GUIDELINES.md). - [x] I've completed the PR template to the best of my ability - [x] I’ve included tests if applicable - [x] I’ve documented my code using [JSDoc](https://jsdoc.app/) format if applicable - [x] I’ve applied the right labels on the PR (see [labeling guidelines](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/LABELING_GUIDELINES.md)). Not required for external contributors. ## **Pre-merge reviewer checklist** - [x] I've manually tested the PR (e.g. pull and build branch, run the app, test code being changed). - [x] I confirm that this PR addresses all acceptance criteria described in the ticket it closes and includes the necessary testing evidence such as recordings and or screenshots.
CLA Signature Action: All authors have signed the CLA. You may need to manually re-run the blocking PR check if it doesn't pass in a few minutes. |
|
|
|
|
completedOnboarding
value (fix: cp-7.50.0 fix infinite loader and inconsistentcompletedOnboarding
value #16695)Description
This PR removes the backfill for
completedOnboarding
that was locatedin
app/store/index.ts
and introduces a newuseCompletedOnboardingEffect
that observesKeyringControllerState.vault
and the current value ofcompletedOnboarding
in order to automatically setcompletedOnboarding
.This ensures that
completedOnboarding
is rightfully set, even when theuser kills the app right before completing onboarding, or during the
reset wallet flow.
Related issues
Fixes: #16638
Related to: https://consensyssoftware.atlassian.net/browse/IDENTITY-152
Manual testing steps
(the last onboarding step)
completedOnboarding
is true, either by verifying thestate logs, or by verifying that account syncing was dispatched
Screenshots/Recordings
Before
After
Pre-merge author checklist
Docs and MetaMask Mobile
Coding
Standards.
if applicable
guidelines).
Not required for external contributors.
Pre-merge reviewer checklist
app, test code being changed).
in the ticket it closes and includes the necessary testing evidence such
as recordings and or screenshots. ca0d327