x86_64 lib is missing (guaranteed to crash on x86_64 devices)

[stevesamknows]

As you are aware, there is no "fallback" for native libs -- i.e. if an x86_64 .so is missing, an
x86_64 device won't simply pick up the corresponding x86 .so, but rather crash immediately.

Inspecting .apk reveals that libobjectbox.so is correctly present for ABIs:

• armeabi-v7a
• arm64-v8a
• x86

but is missing for ABI

• x86_64

(Possibly simply an e.g. .aar packaging oversight?)

Environment:
Android Studio 3.1 Canary 2
ObjectBox 1.2.1

[stevesamknows]

[greenrobot]

That's intentional. Why do you need it?

[stevesamknows]

It's needed for the simple reason that I target x86_64, and there is no "fallback" to 32 bit
libs if the 64 version is missing; the missing .so will trigger immediate crash on x86_64 devices,
as demonstrated when attempting to run app on x86_64 device (Tesco/Pegatron "Hudl2"):

12-04 08:55:31.781 4500-4500/com.myapp.app.beta.debug E/AndroidRuntime: FATAL EXCEPTION: main
    Process: com.myapp.app.beta.debug, PID: 4500
    java.lang.UnsatisfiedLinkError: dalvik.system.PathClassLoader[DexPathList[[zip file \
        "/data/app/com.myapp.app.beta.debug-1/base.apk"],\
        nativeLibraryDirectories=[/data/app/com.myapp.app.beta.debug-1/lib/x86_64, \
        /vendor/lib64, /system/lib64]]] couldn't find "libobjectbox.so"
    at java.lang.Runtime.loadLibrary(Runtime.java:366)
    at java.lang.System.loadLibrary(System.java:988)
    at io.objectbox.internal.NativeLibraryLoader.<clinit>(NativeLibraryLoader.java:44)
    at io.objectbox.BoxStore.<init>(BoxStore.java:177)
    at io.objectbox.BoxStoreBuilder.build(BoxStoreBuilder.java:292)
    at com.myapp.app.application.MyApplication.onCreate(MyApplication.kt:23)
    at android.app.Instrumentation.callApplicationOnCreate(Instrumentation.java:1012)
    at android.app.ActivityThread.handleBindApplication(ActivityThread.java:4557)
    at android.app.ActivityThread.access$1500(ActivityThread.java:151)
    at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1364)
    at android.os.Handler.dispatchMessage(Handler.java:102)
    at android.os.Looper.loop(Looper.java:135)
    at android.app.ActivityThread.main(ActivityThread.java:5258)
    at java.lang.reflect.Method.invoke(Native Method)
    at java.lang.reflect.Method.invoke(Method.java:372)
    at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:903)
    at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:698)

By omitting x86_64, you force your users to drop x86_64 support if they wish to adopt
objectBox -- an unfortunate choice to have to make given the promise of your project.

[greenrobot]

We'll consider this. It's just that there are so few x86 Android devices out there...

[stevesamknows]

Yes please, thank you.

[greenrobot]

Did not understand the x86_64 crash. Do you have other native x86_64 libs? Usually you could ABI filter to only use x86 (never mix 32 vs. 64 bit).

[stevesamknows]

Thank you for following up -- yes, the project I'm working on builds for the "big four" ABIs (armeabi-v7a, arm64-v8a, x86_64 and x86); unfortunately sacrificing x86_64 is not an option.

[stevesamknows]

And a final note -- this issue also applies to projects which don't deliberately build
C++ code; all they need to do is include a 3rd party project that itself bundles a
single x86_64 .so lib (and neglect to strip those libs via gradle packaging options,
something easily overlooked for "pure" java/kotlin projects)

Attached is a simple example for "pure" java/kotlin (no C++) android app which
includes two popular 3rd party dependencies which bring along many native libs:

[stevesamknows]

(if x86_64 omission is about footprint, could add gradle packaging options sample to FAQ --
demonstrating how to eliminate unwanted .so files e.g.

    packagingOptions {
        exclude "lib/x86_64/libobjectbox.so"
}

-- then users incur zero size penalty in their apks)

[greenrobot]

Alright, alright, ... you convinced us... ;-)
1.3.4 will come with x64.

[greenrobot]

Just released 1.3.4 - please let us know if it works for you.

[stevesamknows]

That's great news, will check and report

[stevesamknows]

Verified launch OK on x86_64 device w/objectbox 1.3.4 for project containing
additional 3rd party x86_64 libs -- please close this ticket, thank you again