-
Notifications
You must be signed in to change notification settings - Fork 5k
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
fix: account syncing was not working after upgrading from a previous version #29701
Merged
+148
−6
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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. |
Updated dependencies detected. Learn more about Socket for GitHub ↗︎
|
👍 Dependency issues cleared. Learn more about Socket for GitHub ↗︎ This PR previously contained dependency changes with security issues that have been resolved, removed, or ignored. |
Builds ready [ec946ad]
Page Load Metrics (1766 ± 87 ms)
Bundle size diffs [🚨 Warning! Bundle size has increased!]
|
mathieuartu
changed the title
feat: persist isAccountSyncingReadyToBeDispatched
fix: account syncing after upgrading from a previous version
Jan 14, 2025
mathieuartu
changed the title
fix: account syncing after upgrading from a previous version
fix: account syncing was not working after upgrading from a previous version
Jan 14, 2025
mirceanis
approved these changes
Jan 14, 2025
mirceanis
approved these changes
Jan 14, 2025
cmd-ob
approved these changes
Jan 14, 2025
Builds ready [4728285]
Page Load Metrics (1855 ± 130 ms)
Bundle size diffs [🚨 Warning! Bundle size has increased!]
|
metamaskbot
added
the
release-12.11.0
Issue or pull request that will be included in release 12.11.0
label
Jan 15, 2025
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Account syncing was depending on
_addAccountsWithBalance
to be finished before being triggered.But
_addAccountsWithBalance
was only triggered after onboarding.So people upgrading from a previous version of the extension were not able to use account syncing since
_addAccountsWithBalance
was triggered during their original onboarding, at a time where account syncing was not available.Additionally, the state value
isAccountSyncingReadyToBeDispatched
fromUserStorageController
was not persisted. So people were not able to use account syncing after upgrading their extension version, even coming from a version that had account syncing enabled and working.This PR fixes that, by adding a migration that sets
isAccountSyncingReadyToBeDispatched
to true ifcompletedOnboarding
is true.Also, bumping
@metamask/profile-sync-controller
to versionv4.1.0
will ensure thatisAccountSyncingReadyToBeDispatched
is persisted. (MetaMask/core#5147)Related issues
Fixes: #29679
Manual testing steps
Screenshots/Recordings
Before
After
Pre-merge author checklist
Pre-merge reviewer checklist