You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Explaining the scenario: (where I had identified a bug using this mmkv library)
Replaced the Async-storage with mmkv for utilizing the more size beyond what Async-storage library provides.
Now If user tries to uninstall the App, the cache data still persists and there is no way to identify the uninstall callback to clear the mmkv storage. Still we need to relay on the Async-storage keys to indentify the fresh app install instance and clear the mmkv storage. But opened an issues to find a better way without relaying on the Async-storage library.
This issue was reproduced in only some devices of Android model, not reproducible in iOS though.
The text was updated successfully, but these errors were encountered:
Thanks for bringing this issue up. It seems you’ve encountered a potential bug with mmkv, which is indeed important to address. However, it would help us a lot if you could provide logs from the specific Android devices where this issue occurs.
To gather logs, you can use adb logcat while reproducing the issue on the device. This way, mrousavy can better understand the situation.
Also, if you’d like to ensure more timely support, consider sponsoring the project here. It really helps keep the development going!
Let us know if you can provide the logs!
Note: If you think I made a mistake, please ping @mrousavy to take a look.
Updated Description:
Explaining the scenario: (where I had identified a bug using this mmkv library)
This issue was reproduced in only some devices of Android model, not reproducible in iOS though.
The text was updated successfully, but these errors were encountered: