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
{{ message }}
This repository has been archived by the owner on Nov 7, 2023. It is now read-only.
I'm working on integrating this package in lieu of asyncStorage for some of my stored data. When starting the app i get the following error :
ERROR Error: RNEncryptedStorage is undefined
ERROR Invariant Violation: Module AppRegistry is not a registered callable module (calling runApplication). A frequent cause of the error is that the application entry file path is incorrect.
This can also happen when the JS bundle is corrupt or there is an early initialization error when loading React Native.
ERROR Invariant Violation: Module AppRegistry is not a registered callable module (calling runApplication). A frequent cause of the error is that the application entry file path is incorrect.
This can also happen when the JS bundle is corrupt or there is an early initialization error when loading React Native.
I thought something was wrong with my inplementation, but it appears that the issue is on the installation part.
When i run either pod installor npx pod-installthe package name is not in the list.
Is this a known thouble of the platform ? Is there any solution for this issue ?
Thanks !
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hello !
I'm working on integrating this package in lieu of asyncStorage for some of my stored data. When starting the app i get the following error :
I thought something was wrong with my inplementation, but it appears that the issue is on the installation part.
When i run either
pod install
ornpx pod-install
the package name is not in the list.Is this a known thouble of the platform ? Is there any solution for this issue ?
Thanks !
The text was updated successfully, but these errors were encountered: