-
-
Notifications
You must be signed in to change notification settings - Fork 238
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
Fails silently when using bad path #464
Comments
Oh that's interesting. Is there something being printed to Xcode Logs / Android Logcat? |
Ahh yes there is:
I'll pay more attention to the iOS log when debugging 🕵️♂️ Still would be nice to see these bubble up to the JS log |
No, lol that would be pretty annoying as it spams a lot. A native library logs to the native console.
But yea that's weird. I wonder why that doesn't throw. |
Does this issue still persist? |
When creating MMKV with a bad path e.g.
This call succeeds
However the data is not actually stored
As an aside would be nice to have some examples with valid paths or link to docs about what paths are allowed :)
Or maybe export
DocumentDir
or something likereact-native-fs
?The text was updated successfully, but these errors were encountered: