M.MMKC.delete is not a function - Android Release Mode about react-native-mmkv HOT 13 CLOSED

This might be related to #28 because the current way of installing the JSI bindings is a bit hacky. I'll rewrite this thing to a TurboModule, which should fix those issues.

from react-native-mmkv.

Okay just checked out the logs, I'm wondering what the prefix means? (aka the s. in s.MMKV.set) Is that just a thing Sentry does or is there something wrong with the import?

from react-native-mmkv.

Can you check if the newest version (1.1.6) works for you? Note that it requires some additional installation steps, see INSTALL.md.

Also, if you can't import the library see this issue which includes a temporary workaround. I'll find a fix that requires no native changes at all soon 👍

from react-native-mmkv.

M.MMKC.delete is not a function

is that actually the error? I don't think I had a typo in there 🤨

from react-native-mmkv.

Also, please create a reproduceable sample app for this, I have no way of debugging that. Can you absolutely not reproduce it in debug mode? Maybe try upgrading react-native to 0.64?

from react-native-mmkv.

Okay just checked out the logs, I'm wondering what the prefix means? (aka the s. in s.MMKV.set) Is that just a thing Sentry does or is there something wrong with the import?

Sentry does this. Sorry for the small debug information that sentry gives on share mode.

from react-native-mmkv.

Also, please create a reproducible sample app for this, I have no way of debugging that. Can you absolutely not reproduce it in debug mode? Maybe try upgrading react-native to 0.64?

Debug works like a charm, but on release mode in this specific user, this happens, I will try to upgrade RN to see if I can catch some way to reproduce this.

from react-native-mmkv.

More information about the crash:

from react-native-mmkv.

This is currently happening for me even in DEBUG (Android) when I upgrade to 1.0.11. Everything works on version 1.0.10.

from react-native-mmkv.

@mrousavy is there also a temporary workaround for iOS? I think the JSI bindings problem affect both platforms

from react-native-mmkv.

@ChrisEelmaa I haven't seen any issues on the iOS platform, so I don't think there's something wrong there. Are you experiencing crashes?

Of course I will still migrate it to TurboModules as soon as possible.

from react-native-mmkv.

I am not directly using this library however I have taken a look at how you install the iOS bindings as well your thread (facebook/react-native#31197), and am fairly confident that is not the correct way, as I also install the iOS bindings like that, and occasionally there is a race condition, I managed to reproduce it 2 times out of 300 or so, but essentially what I believe is happening is that the code

jsiRuntime.global().setProperty(jsiRuntime, "mmkvGet", ....);

gets executed too soon/too late sometimes, and in that case the global.mmkvGet is not available, and won't be available throughout the app

from react-native-mmkv.

Exactly, it is not the correct way. The correct way would be by using TurboModules, but they're not fully ready yet so we have to use this JSI install workaround. If there are also race conditions for iOS I could take a look on how I can install it there, if you find something out let me know

from react-native-mmkv.