-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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: Migrate AsyncStorage to mmkv #10153
base: main
Are you sure you want to change the base?
Conversation
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. |
Co-authored-by: tommasini <[email protected]>
Co-authored-by: tommasini <[email protected]>
Co-authored-by: tommasini <[email protected]>
…sk-mobile into kylan/mmkv-final
Proof of proper migration via simulator, pardon the data structure difference (array vs object). AsyncStorage before:
mmkv after:
|
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great PR!
One small question, Will the renaming of async-storage-wrapper.js be handled in a separate ticket?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm wondering if we should clear all the async storage, after migrating
https://react-native-async-storage.github.io/async-storage/docs/api#clear
WDYT?
|
|
Description
While debugging a sqlite error related to AsyncStorage (surpassing storage limit on Android) we have decided to migrate from AsyncStorage to mmkv due to it not having said issue and also for performance reasons. This includes an actual migration of any existing items saved in AsyncStorage to mmkv
Related issues
Fixes: https://github.com/orgs/MetaMask/projects/60/views/6?pane=issue&itemId=63268337
Manual testing steps
EXISTING_USER
flow (since that value is taken from mmkv now)Screenshots/Recordings
Should be no discernible different in application behavior.
Pre-merge author checklist
Pre-merge reviewer checklist