search

gusgard / react-native-devsettings

Enable react-native-debugger and chrome debugger on Hermes
Apache License 2.0
127 stars 3 forks source link

error message #8

Open JsonKit opened 9 months ago

JsonKit commented 9 months ago

Failed to create a new MMKV instance: React Native is not running on-device. MMKV can only be used when synchronous method invocations (JSI) are possible. If you are using a remote debugger (e.g. Chrome), switch to an on-device debugger (e.g. Flipper) instead.

gusgard commented 7 months ago

Please, share the react native version you are using

ramonxm commented 7 months ago

same issue,

versions: "react-native": "0.73.4", "react-native-mmkv": "^2.12.1",

ramonxm commented 7 months ago

Captura de Tela 2024-02-23 às 11 59 26

StasSokolov1 commented 6 months ago

same issue

gusgard commented 6 months ago

I didn't have time to test it yet but React Native stopped supporting the internal API I was calling, I will create a new release soon with the fix for v0.73

yinminqian commented 6 months ago

开启了本插件以后，是不是就不会使用hermes引擎了

Lakston commented 4 months ago

any news on a release working with RN 73+ ?

jehillert-ziosk commented 1 month ago

Not sure this is the place to look for a work-around. The mmkv-react-native lists remote-debugging as a hard limitation. It would be awesome if it did fix it, but even if it does, we would probably still need the mmkv authors to turn off the warning. I've set up redux devtools using async-storage, and separately used mmkv for large files. If there is any instance of mmkv being used at all, anywhere in the app, it will throw the warning.