8000 chore(runway): cherry-pick fix: cp-7.50.0 fix infinite loader and inconsistent `completedOnboarding` value by runway-github[bot] · Pull Request #16726 · MetaMask/metamask-mobile · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

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

Merged
merged 3 commits into from
Jun 27, 2025

Conversation

runway-github[bot]
Copy link
Contributor
@runway-github runway-github bot commented Jun 26, 2025

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

Before

After

Pre-merge author checklist

Pre-merge reviewer checklist

  • I've manually tested the PR (e.g. pull and build branch, run the
    app, test code being changed).
  • 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. ca0d327

…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.
@runway-github runway-github bot requested review from a team as code owners June 26, 2025 20:11
Copy link
Contributor

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.

@tommasini tommasini added the Run Smoke E2E Requires smoke E2E testing label Jun 26, 2025
Copy link
Contributor
github-actions bot commented Jun 26, 2025

https://bitrise.io/ Bitrise

❌❌❌ pr_smoke_e2e_pipeline failed on Bitrise! ❌❌❌

Commit hash: be620de
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/00b086ba-447d-489e-929e-ff9d069da712

Note

  • You can kick off another pr_smoke_e2e_pipeline on Bitrise by removing and re-applying the Run Smoke E2E label on the pull request

Tip

  • Check the documentation if you have any doubts on how to understand the failure on bitrise

@tommasini tommasini added Run Smoke E2E Requires smoke E2E testing and removed Run Smoke E2E Requires smoke E2E testing labels Jun 27, 2025
Copy link
Contributor
github-actions bot commented Jun 27, 2025

https://bitrise.io/ Bitrise

❌❌❌ pr_smoke_e2e_pipeline failed on Bitrise! ❌❌❌

Commit hash: 5107672
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/f923c6e7-d76a-4ba0-9e09-8de2f985c7e6

Note

  • You can kick off another pr_smoke_e2e_pipeline on Bitrise by removing and re-applying the Run Smoke E2E label on the pull request

Tip

  • Check the documentation if you have any doubts on how to understand the failure on bitrise

@tommasini tommasini added Run Smoke E2E Requires smoke E2E testing and removed Run Smoke E2E Requires smoke E2E testing labels Jun 27, 2025
Copy link
Contributor
github-actions bot commented Jun 27, 2025

https://bitrise.io/ Bitrise

✅✅✅ pr_smoke_e2e_pipeline passed on Bitrise! ✅✅✅

Commit hash: 7c3fa9e
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/0f997859-2fd1-4786-83ba-3bbeb9a637a3

Note

  • You can kick off another pr_smoke_e2e_pipeline on Bitrise by removing and re-applying the Run Smoke E2E label on the pull request

Copy link

@tommasini tommasini merged commit bc87991 into release/7.50.0 Jun 27, 2025
47 of 49 checks passed
@tommasini tommasini deleted the runway-cherry-pick-7.50.0-1750968654 branch June 27, 2025 16:53
@github-actions github-actions bot locked and limited conversation to collaborators Jun 27, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Run Smoke E2E Requires smoke E2E testing team-runway-bot
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants
0