-
Notifications
You must be signed in to change notification settings - Fork 585
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
java.lang.UnsatisfiedLinkError: couldn't find DSO to load: librealm.so #5521
Comments
@somasekharkakarla The error message is a bit odd but in order to use v11.5.1, you will have to update React Native. Please check the compatibility matrix |
Thanks for pointing out that our |
Hi @kneth "react-native": "0.68.5", Also I am using ndk version 23.0.7599858 I have referred this link to pick the above realm version. I am able to generate a signed apk build on Android but immediately on app launch I am getting the same error Error: Exception in HostObject::get for prop 'Realm': java.lang.UnsatisfiedLinkError: couldn't find DSO to load: librealm.so caused by: io.realm.react.util.SSLHelper result: 0, js engine: Anything we can do to resolve this issue? |
Hello @shridhar48 , Try adding |
Hi I'm facing the same issue, here are my configurations: I am using: realm: 11.10.1 ` `
|
Hi @nabilashraf , I tried @vijaydokrimare-gep solution by adding following line to proguard-rules.pro file |
Unfortunately, for me it didn't work. It still crashes the app. |
This should be added to the Documentation |
How frequently does the bug occur?
Always
Description
App crashes after updating realm to from 11.0.0 > 11.5.1.
For React Native:
"react": "18.1.0",
"react-native": "0.70.5",
"realm": "11.5.1",
For Android:
Stacktrace & log output
Can you reproduce the bug?
Always
Reproduction Steps
just update from 11.0.0 > 11.5.1
Version
11.5.1
What services are you using?
Local Database only
Are you using encryption?
No
Platform OS and version(s)
android 13
Build environment
Which debugger for React Native: ..
Cocoapods version
No response
The text was updated successfully, but these errors were encountered: