fix: Fix migration 120.3 error caused by invalid state#26485
Merged
fix: Fix migration 120.3 error caused by invalid state#26485
Conversation
For a small number of users, migration 120.3 is failing due to invalid `TransactionController.transactions` state. We aren't sure yet how this is happening, but we can resolve the problem by updating the migration to delete this invalid state if we detect it. No other state relies on this state, and if it's invalid it won't work properly anyway. The migration has been renamed from 120.3 to 120.6 so that it will be re-run for any users who encountered this migration on v12.0.1 already. Fixes #26423
|
Collaborator
Builds ready [b47d2af]
Page Load Metrics (89 ± 14 ms)
Bundle size diffs [🚀 Bundle size reduced!]
|
danjm
approved these changes
Aug 19, 2024
DDDDDanica
approved these changes
Aug 19, 2024
This file contains hidden or 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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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
For a small number of users, migration 120.3 is failing due to invalid
TransactionController.transactionsstate. We aren't sure yet how this is happening, but we can resolve the problem by updating the migration to delete this invalid state if we detect it. No other state relies on this state, and if it's invalid it won't work properly anyway.The migration has been renamed from 120.3 to 120.6 so that it will be re-run for any users who encountered this migration on v12.0.1 already.
Related issues
Fixes #26423
Manual testing steps
dist/chromedirectory and proceed through onboardingchrome.storage.local.get(console.log)to check that the transactions state has been removed.Screenshots/Recordings
N/A
Pre-merge author checklist
Pre-merge reviewer checklist