-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
com.getkeepsafe.relinker.MissingLibraryException: lib/armeabi-v7a/librealm-jni.so #3484
Comments
@blackkara Sorry we are a bit busy recently, so the reply is quite slow. On what kind of device do you get this crash? |
Info moved from #3447 GoalTo find a solution for abi related problems Expected ResultsTo run all split versions of app successfully Actual ResultsCrashlytics http://crashes.to/s/25d21237c1a
Version of Realm and toolingRealm version(s): 1.2.0 Android Studio version: 2.1.3 Which Android version and device: Related values could be seen in the Crashlytics above link My QuestionI saw a related link #3175 about this issue, but they are saying that user(s) trying to install an split version of app on wrong device manually.
|
I had opened a topic on stackoverflow probably related to my issue too, really don't know what i did wrong. I'm even started getting this "Couldn’t load librealm-jni.so" error on my real test devices (previously they were working) Thanks for interest |
uh, you are using ABI split. Would you please give us some detailed information about those device models? There is a chance if those devices doesn't support |
And the question on stackoverflow is solved I think? I am confused, it seems not related with the question here. |
For example this is my one of the real test devices. Before i never get an error from this device, but now getting. Device : Samsung GT-P3105 An important thing, if i remove whole split section from gradle, then it works on this device |
good! so you can actually reproduce it!
|
I am at a loss for words, now all real test devices working. But couldn't find a solution for crashes on crashlytics
|
Only if you have another native library in your code, one that doesn't support 64-bit. But that would be a whole different problem altogether. Personally I haven't had this kind of crash at all and the production app also uses Relinker. |
@Zhuinden In my case, the only native library is librealm-jni.so So, can i say that converting to single APK could solve this issue for me ? |
I think so! |
Seems like the only way to get rid of this issue is switching to single APK for me. Thanks @Zhuinden |
@blackkara Would you please do a And also, seems KeepSafe/ReLinker@079eef0 this will fix some problems as well. I will update relinker to 1.2.2 |
@blackkara We upgraded to Relinker 1.2.2. Can you try to use |
@beeender, the result of Samsung GT-P3105
|
Firstly, let me telling a little story I'm having a painful issue on my android studio. I have a few devices that have different architectures(as might be expected). And i can run the app on these devices. But after a time, when i try to run the app on these devices again (via android studio's run button), studio sends wrong apk distribution. As a result, i'm getting the librealm-jni.so error. http://stackoverflow.com/questions/39727835/android-studio2-2-sends-wrong-abi-split-to-device So, the above mentioned my test device (Samsung GT-P3105), could face this issue due to studio's weird behavior. The story finished. Now, i have tried 1.2.0 and 2.0.0-SNAPSHOT versions. They worked perfectly on my test devices. But i have to consider devices that face librealm-jni.so related issues on market. librealm-jni.so related issue |
I got a problem the same as you , so , did you solve it? |
@Botasky369 I couldn't find and make any reasonable cure for devices on market (mentioned above in crashlytic links) I'll just update realm version to 2.0.0 on my app, then wait to get less librealm-jni.so related crashes. |
@blackkara OK, thanks |
@blackkara you should wait until 2.0.1 |
2.0.1 has been released |
The same error occurs after upgrading from v1.2.0 to v2.0.x. I tried both v2.0.1 and v2.0.2, but did not solved this issue. InfoAndroid Studio version: 2.2 |
I didn't upgrade realm on my app, after i will share feedback here. Thanks @cmelchior, @Zhuinden @kuno Are you getting this issue from users(market etc) or your test devices ? If test devices, i suggest you checking this link. Because, when you press the start button from android studio, it sends wrong abi split to device |
Hello, I Fatal Exception: java.lang.RuntimeException: Unable to create application com.cashdivider.app.application.CashdividerApp: com.c.a.b: lib/armeabi-v7a/librealm-jni.so Is this been fixed? If yes, in which version? Or what I can do? Thank you |
@cotfas Check out this link http://stackoverflow.com/questions/39727835/android-studio2-2-0-and-2-2-1-sends-wrong-abi-split-to-device I was getting the same error. I just rebuilt my project and ran my app again, it sorted it out. |
Can you tell me what version of Android do you use? And what gradle version? Thank you |
My gradle version is 2.2.1, Android Studio 2.2.1; also Realm 2.0.2 |
@cotfas PS: I ran into this issue again. Had to rebuild&run it 4-5 times to get it working. |
Same problem here, happening on devices. |
Realm 2.x doesn't support regular 'armeabi' (yet) so if you have abiSplit for Or just stick to Realm 1.1.1 or 1.2.0 in the meantime |
@Zhuinden How often |
@ppamorim There is an issue tracking it here #3506 but it'll take a while, I think. If you read above, you'll see that |
@Zhuinden Thank you for the explanation, you solved my problem and everything is working now. |
@ppamorim I... did? What was the fix? |
@Zhuinden I got same problem when I upgrade realm 1.1.0 to 2.2.1.'Realm 2.x doesn't support regular 'armeabi' (yet) so if you have abiSplit for armeabi then you should probably remove it' is correct.And the answer is |
Hi there, just chiming in:
|
Randomly seeing this lately :( Not using ABI splits, and a clean & build fixes it. On Android Studio 3.0 Beta 6. Let me know if you need any more details. |
|
|
|
|
We have a situation like that of @zoltish . We don't use instant run. |
@toktogul but do you use AbiSplits? |
we don't use |
@beeender Seems that I am running on a x86 device after all, my mistake. ADB:
Full crash log:
|
|
@beeender Yup, its empty. |
@zoltish My guess is there is something wrong with your Android Studio setup ... |
@beeender Might be, not that I would know what that might be but I am running the beta version of it after all. Everything works completely fine, with this being the exception every 10-15 hours or so. |
@beeender 's answer is right for me. I forget to add the line "jniLibs.srcDirs = ['libs']" in the gradle file. |
In some android devices the cpu abi code returns "armabi" as there is not library for that it fails. I will like to overload it with custom relinker so that in case it fails I can specify which jni lib to load, however it is very difficult to override the classpath in build.gradle what will you guys suggest? |
@softwarejoint did you try to apply Realm manually (without the plugin) https://realm.io/docs/java/latest#how-do-i-customize-dependecies-defined-by-the-realm-gradle-plugin then exclude the transitive dependency to Alternatively, you can build Realm locally & replace with the dependency yourself https://github.com/realm/realm-java#building-realm |
This is my second topic about same issue, no one saw #3447
In my app, the only native library is realm's librealm-jni.so, and seems like this is not cure for me couldnt-load-librealm-jniso
I'm still getting crash logs related this issue. How can i deal with this issue ?
Goal
To find a solution for ABI related problems
Expected Results
To run all split versions of app successfully
Actual Results
Version of Realm and tooling
Realm version(s): 1.2.0
Android Studio version: 2.2
The text was updated successfully, but these errors were encountered: