Recent exception on 2 real Android 11 device with 0.16 release / library "libvtm-jni.so" not found

[carlos-mg89]

I've recently received 3 crashes that's seem a bit odd. It looks like the app cannot find the VTM library.

The device has the following specs:

• Brand: Samsung
• Model: Galaxy A32 5G / Galaxy A20s
• OS version: Android 11
• Free RAM: +3GB / +1GB
• Free disc: +90GB / +40GB

I've checked what kind of processor have these devices. One of them has this one (https://www.qualcomm.com/products/snapdragon-450-mobile-platform) which looks like an ARM 64.

I can see the following VTM library versions added in my app bundle with libvtm-jni.so and libgdx.so on each folder:

• arm64-v8a
• armeabi-v7a
• x86
• x86_64

Some more relevant data:

• This issue has been tracked 3 times on these 2 real devices during the last week, after I released an update that contains VTM 0.16. Not many people have tried this update yet, about 145 app installs since the release of the update.
• The previous update of my app had VTM 0.13 (and had had 0 of these issues during the last year and a half with thousands of app installs)

The only relevant change I see in my app is that I'm using now Android View Binding. Although I've never experienced myself an issue with my real devices or the Android emulators (tested on Android 7, 10 and 11).

This is the stack trace:

Caused by java.lang.UnsatisfiedLinkError: dlopen failed: library "libvtm-jni.so" not found
       at java.lang.Runtime.loadLibrary0(Runtime.java:1087)
       at java.lang.Runtime.loadLibrary0(Runtime.java:1008)
       at java.lang.System.loadLibrary(System.java:1664)
       at org.oscim.android.MapView.init(MapView.java:82)
       at org.oscim.android.MapView.<init>(MapView.java:101)
       at java.lang.reflect.Constructor.newInstance0(Constructor.java)
       at java.lang.reflect.Constructor.newInstance(Constructor.java:343)
       at android.view.LayoutInflater.createView(LayoutInflater.java:852)
       at android.view.LayoutInflater.createViewFromTag(LayoutInflater.java:1004)
       at android.view.LayoutInflater.createViewFromTag(LayoutInflater.java:959)
       at android.view.LayoutInflater.rInflate(LayoutInflater.java:1121)
       at android.view.LayoutInflater.rInflateChildren(LayoutInflater.java:1082)
       at android.view.LayoutInflater.rInflate(LayoutInflater.java:1124)
       at android.view.LayoutInflater.rInflateChildren(LayoutInflater.java:1082)
       at android.view.LayoutInflater.inflate(LayoutInflater.java:680)
       at android.view.LayoutInflater.inflate(LayoutInflater.java:532)
       at com.walkaholic.hikeapp.databinding.MapActivityBinding.inflate(MapActivityBinding.java:155)
       at com.walkaholic.hikeapp.databinding.MapActivityBinding.inflate(MapActivityBinding.java:149)
       at com.walkaholic.hikeapp.framework.ui.activities.MapActivity.onCreate(MapActivity.java:80)
       at android.app.Activity.performCreate(Activity.java:8198)
       at android.app.Activity.performCreate(Activity.java:8182)
       at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1309)
       at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:3765)
       at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:3968)
       at android.app.servertransaction.LaunchActivityItem.execute(LaunchActivityItem.java:85)
       at android.app.servertransaction.TransactionExecutor.executeCallbacks(TransactionExecutor.java:135)
       at android.app.servertransaction.TransactionExecutor.execute(TransactionExecutor.java:95)
       at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2307)
       at android.os.Handler.dispatchMessage(Handler.java:106)
       at android.os.Looper.loop(Looper.java:246)
       at android.app.ActivityThread.main(ActivityThread.java:8512)
       at java.lang.reflect.Method.invoke(Method.java)
       at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:602)
       at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1130)

[carlos-mg89]

I've found what it looks like some relevant information: microg/GmsCore#19

This made me think that perhaps someone is running my app on a non official Android ROM.

So I've dig into the most recent register of the above crash, and it happened on an Android 8.1 (LG Nexus 5x). It seems this telephone never got an official Android 8.1 ROM from LG. However it did get several unofficial Android 8.1 ROMS: https://www.getdroidtips.com/android-8-1-oreo-nexus-5x/

I've tried running my app using an emulator without the Google Play services, and it runs OK.

But the above got me thinking it might be the case. Someone is trying to run the app under a non-official ROM.

However, this won't explain why the above Samsung Galaxy A32 5G and Samsung Galaxy A20s (both received Google's Android 11) had these crashes.

[devemux86]

How do you integrate the native libraries in your app?
With their jars like in the integration guide?
Or you could extract and integrate them directly in the proper app dirs.

Do you use Android multidex in your app?

Why having libGDX native libs, do you use vtm-android-gdx?

[carlos-mg89]

Hi Emux,

Yes, I followed the integration guide.

Yes, I use Android multidex.

I'm not entirely sure about why I included the libGDX packages. But I did. I'm using online vector tiles (.pbf files served from an online server of myself) and custom Mapsforge files (generated by myself with Osmosis and other tools). Perhaps I don't need the libGDX packages?

Over the map, I have PathLayer, ItemizedLayer (for markers) and some other stuff.

This is the relevant build.gradle code:

    def vtmVersion = '0.16.0'
    def gdxVersion = '1.10.0'

    implementation 'com.android.support:multidex:1.0.3' // So yes, I use multidex

    implementation "com.badlogicgames.gdx:gdx:$gdxVersion"
    implementation "com.badlogicgames.gdx:gdx-backend-android:$gdxVersion"

    implementation "org.mapsforge:vtm:$vtmVersion"
    implementation "org.mapsforge:vtm-themes:$vtmVersion"
    implementation "org.mapsforge:vtm-android:$vtmVersion"
    implementation "org.mapsforge:vtm-android:$vtmVersion:natives-armeabi-v7a"
    implementation "org.mapsforge:vtm-android:$vtmVersion:natives-arm64-v8a"
    implementation "org.mapsforge:vtm-android:$vtmVersion:natives-x86"
    implementation "org.mapsforge:vtm-android:$vtmVersion:natives-x86_64"
    implementation "org.mapsforge:vtm-android-mvt:$vtmVersion"
    implementation "org.mapsforge:vtm-gdx:$vtmVersion"
    implementation "org.mapsforge:vtm-android-gdx:$vtmVersion"
    implementation "org.mapsforge:vtm-android-gdx:$vtmVersion:natives-armeabi-v7a"
    implementation "org.mapsforge:vtm-android-gdx:$vtmVersion:natives-arm64-v8a"
    implementation "org.mapsforge:vtm-android-gdx:$vtmVersion:natives-x86"
    implementation "org.mapsforge:vtm-android-gdx:$vtmVersion:natives-x86_64"
    implementation "org.mapsforge:vtm-http:$vtmVersion"
    implementation "org.mapsforge:vtm-mvt:$vtmVersion"

    implementation 'net.sf.kxml:kxml2:2.3.0'
    implementation 'org.slf4j:slf4j-api:1.7.29'
    implementation 'com.caverock:androidsvg:1.4'

Thank you for looking into this.

[devemux86]

Perhaps I don't need the libGDX packages?

Normally you do not need it, vtm-android has more features.
See the integration guide and use only the "Core" + "Android" sections and possibly the extra sections for JTS, online tiles, etc..

I use Android multidex.

This may be the cause for various problems.
If you have min API level 21 in your app you could remove it.

[carlos-mg89]

Yeap, I've tested it without the libgdx packages and everything seems to work as it was. I cannot really say if better, worse or just the same. When I first added the libgdx packages, after reading their website, I thought that adding those packages will increase the library performance to draw 2D and 3D elements.

Will give it a try without these packages.

About multidex, I actually have minSdkVersion 21. So will try without multidex as well.

Will write down after some days or weeks, and see if the exception is gone for good.

[devemux86]

The recommended vtm-android uses Android backend.
vtm-android-gdx uses the libGDX backend.

There are samples in vtm-android-example to see them.

[carlos-mg89]

It seems the issue hasn't gone away. A user with a Nexus 5X and Android 8.1 has had 4 crashes of the above missing libvtm-jni.so.

The first 3 times, it was with previous versions of the app that included the vtm-android-gdx packages. But the latest one is with the package that contains the change that removes MultiDEX and the vtm-android-gdx packages.

Any other idea about why could this be happening?

[carlos-mg89]

Keeps happening although it's for a low quantity of devices. Quite clear that no concrete device nor brand is involved (which makes this issue more general).

Any help would be very appreciated.