Skip to content
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

Caused by j8.b: Could not find 'librealm-jni.so'. Looked for: [arm64-v8a, armeabi-v7a, armeabi], but only found: []. #7767

Open
adaonder opened this issue Feb 10, 2023 · 12 comments

Comments

@adaonder
Copy link

How frequently does the bug occur?

Sometimes

Description

Caused by j8.b: Could not find 'librealm-jni.so'. Looked for: [arm64-v8a, armeabi-v7a, armeabi], but only found: [].
at com.getkeepsafe.relinker.ApkLibraryInstaller.installLibrary(ApkLibraryInstaller.java:173)
at com.getkeepsafe.relinker.ReLinkerInstance.loadLibraryInternal(ReLinkerInstance.java:180)
at com.getkeepsafe.relinker.ReLinkerInstance.loadLibrary(ReLinkerInstance.java:136)
at com.getkeepsafe.relinker.ReLinker.loadLibrary(ReLinker.java:70)
at com.getkeepsafe.relinker.ReLinker.loadLibrary(ReLinker.java:57)
at io.realm.internal.RealmCore.loadLibrary(RealmCore.java:60)
at io.realm.Realm.initializeRealm(Realm.java:348)
at io.realm.Realm.init(Realm.java:263)
at com.globme.common.data.local.realm.LocalRealmDB.realConfiguration(LocalRealmDB.java:27)
at com.globme.timeware.application.Application.onCreate(Application.java:34)
at android.app.Instrumentation.callApplicationOnCreate(Instrumentation.java:1192)
at android.app.ActivityThread.handleBindApplication(ActivityThread.java:7233)
at android.app.ActivityThread.access$1700(ActivityThread.java:292)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2172)
at android.os.Handler.dispatchMessage(Handler.java:106)
at android.os.Looper.loop(Looper.java:255)
at android.app.ActivityThread.main(ActivityThread.java:8224)
at java.lang.reflect.Method.invoke(Method.java)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:632)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1049)

Stacktrace & log output

Caused by j8.b: Could not find 'librealm-jni.so'. Looked for: [arm64-v8a, armeabi-v7a, armeabi], but only found: [].
       at com.getkeepsafe.relinker.ApkLibraryInstaller.installLibrary(ApkLibraryInstaller.java:173)
       at com.getkeepsafe.relinker.ReLinkerInstance.loadLibraryInternal(ReLinkerInstance.java:180)
       at com.getkeepsafe.relinker.ReLinkerInstance.loadLibrary(ReLinkerInstance.java:136)
       at com.getkeepsafe.relinker.ReLinker.loadLibrary(ReLinker.java:70)
       at com.getkeepsafe.relinker.ReLinker.loadLibrary(ReLinker.java:57)
       at io.realm.internal.RealmCore.loadLibrary(RealmCore.java:60)
       at io.realm.Realm.initializeRealm(Realm.java:348)
       at io.realm.Realm.init(Realm.java:263)
       at com.globme.common.data.local.realm.LocalRealmDB.realConfiguration(LocalRealmDB.java:27)
       at com.globme.timeware.application.Application.onCreate(Application.java:34)
       at android.app.Instrumentation.callApplicationOnCreate(Instrumentation.java:1192)
       at android.app.ActivityThread.handleBindApplication(ActivityThread.java:7233)
       at android.app.ActivityThread.access$1700(ActivityThread.java:292)
       at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2172)
       at android.os.Handler.dispatchMessage(Handler.java:106)
       at android.os.Looper.loop(Looper.java:255)
       at android.app.ActivityThread.main(ActivityThread.java:8224)
       at java.lang.reflect.Method.invoke(Method.java)
       at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:632)
       at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1049)

Can you reproduce the bug?

-- select --

Reproduction Steps

No response

Version

10.13.2-transformer-api

What Atlas App Services are you using?

Local Database only

Are you using encryption?

No

Platform OS and version(s)

Android 12

Build environment

Android Studio version: Android Studio Electric Eel | 2022.1.1 Patch 1
Android Build Tools version: Build #AI-221.6008.13.2211.9514443, built on January 21, 2023
Gradle version: gradle:7.4.1

@cmelchior
Copy link
Contributor

Hi @adaonder

We have seen this happen in a few cases:

  • If you are using App Bundles and are using an APK that was copied from another device. This usually requires a rooted device.
  • If the app was downloaded from a 3rd party app store that didn't package the so files correctly (see above).
  • If you are running the app in an emulator that don't match exactly the architecture you are building for.

All of these things are unfortunately outside our control.

If you somehow are able to reproduce this, we would love to get the details.

@sync-by-unito sync-by-unito bot added Waiting-For-Reporter Waiting for more information from the reporter before we can proceed More-information-needed More information needed from the reporter. The issue will autoclose if no more information is given. labels Feb 13, 2023
@adaonder
Copy link
Author

Hi @cmelchior

I think the source of the problem is app bundles(.aab). I download the app from Google Play Store.
The problem comes out like that, but it doesn't always happen.
it happened on first install, i saw samsung galaxy s10 lite with android 12 once then i couldn't catch it again.
I was using google room db now I am using real library.

@github-actions github-actions bot added Needs-Attention and removed More-information-needed More information needed from the reporter. The issue will autoclose if no more information is given. Waiting-For-Reporter Waiting for more information from the reporter before we can proceed labels Feb 13, 2023
@edualonso
Copy link
Contributor

Hi @adaonder
Unfortunately we can't help you with this unless you provide us with a way to reproduce the error. Please let us know if you find a way to do it.

@sync-by-unito sync-by-unito bot added the More-information-needed More information needed from the reporter. The issue will autoclose if no more information is given. label Feb 16, 2023
@Koster35
Copy link

Koster35 commented Mar 2, 2023

Hi, we just started seeing this same issue today in our Crashlytics console.
We are using Realm 10.10.1 and have been for about a year now, but haven't seen this appear until today. We deploy our app using AABs, rather than APKs.
So far, it has only appeared on Android 8 and 10 devices. LGE Nexus 5X devices running Android 8.1 are most affected. No device this has occurred on is rooted.

We have not reproduced this issue ourselves, but I will provide more information as I am able to. Thanks.

@github-actions
Copy link

github-actions bot commented Mar 3, 2023

This issue has been automatically closed because there has been no response to our request for more information from the original author. With only the information that is currently in the issue, we don't have enough information to take action. Please reach out if you have or find the answers we need so that we can investigate further.

@github-actions github-actions bot closed this as completed Mar 3, 2023
@github-actions github-actions bot removed the More-information-needed More information needed from the reporter. The issue will autoclose if no more information is given. label Mar 3, 2023
@github-actions github-actions bot reopened this Mar 3, 2023
@adaonder
Copy link
Author

adaonder commented Mar 3, 2023

@edualonso this method Realm.init(context); I was getting it when I typed it in Application. Now I wrote it in Activity I no longer get this error.

@clementetb
Copy link
Collaborator

I couldn't reproduce the issue by deploying an app bundle with Realm on a Samsung S9 (Android 10) and on a Samsung A70 (Android 11).

@onderadaidenfit
Copy link

@clementetb

I already saw it by chance once, it didn't happen yet. It was constantly coming up on firebase.

@onderadaidenfit
Copy link

maybe there is a bug in android. But I first saw this error in your library. There was this error when the application was in the extended class. The command there is Realm.init().

@adaonder
Copy link
Author

@cmelchior, @clementetb, You can close this thread if you want. because this error hasn't come yet since I changed my code.

@clementetb
Copy link
Collaborator

Initializing the code in Application shouldn't be the issue.

@adaonder On what callback were you invoking Realm.init, was it on onCreate or attachBaseContext?

@adaonder
Copy link
Author

adaonder commented Mar 21, 2023

@clementetb

Old Code:

class Application extends MultiDexApplication ;

`@Override
public void onCreate() {

    super.onCreate();
    instance = this;
    LocalRealmDB.getInstance().realConfiguration(getApplicationContext());
    
}`


And

LocalRealmDB class; 

`public static LocalRealmDB getInstance() {
    return new LocalRealmDB();
}`

`public void realConfiguration(Context context) {

    Realm.init(context);
    
    RealmConfiguration configuration = new RealmConfiguration.Builder().schemaVersion(SCHEMA_V_NOW).name(realmName).build()
    
    Realm.setDefaultConfiguration(configuration);
    
}`

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants