Android cannot find the library on some devices.

[WilsontheWolf]

I currently distribute a modified version of love for use of modding Balatro on mobile devices. One of the changes I use is including lua-https so mods can use it. However on some devices it fails to find the module.

I originally thought this was due to 32 bit devices but this device is definitly 64 bit. This particular case this is on a nothing phone (2a) android 15. My personal device (Google pixel 9, GrapheneOS, Android 16) works perfectly fine.

My modified source is here:

• https://github.com/WilsontheWolf/lmm-love-android
• https://github.com/WilsontheWolf/lmm-love

The compiled APK is also available here: https://lmm.shorty.systems/base.apk

The no game screen has been modified to test https, which should aid in any testing you may be doing.

Any insight would be much appreciated, thanks

[MikuAuahDark]

Can you print the output of love.filesystem.getCRequirePath()? Also is there a logcat for the problematic device?

[WilsontheWolf]

love.filesystem.getCRequirePath() returns ?? for both devices. Here is a logcat from running the nogame screen:

logcat.log.txt

[MikuAuahDark]

I wonder if you can single-step in here using Android studio? https://github.com/WilsontheWolf/lmm-love/blob/01af71f2f4c33dd08533296d7a66dce0ab520b52/src/modules/filesystem/wrap_Filesystem.cpp#L802

Preferably on the device where https.so fails to load.

[WilsontheWolf]

Hopefully this is what you need

[MikuAuahDark]

Yep, and try single-step after handle = SDL_LoadObject(...) and see if handle is null pointer or not.

[WilsontheWolf]

It was not a null pointer. However, after testing, it appears the issues does not appear on debug builds, just release builds. Not sure its possible to debug a release build

[MikuAuahDark]

You can try adding calls to SDL_Log around it that will appear in the logcat.

[WilsontheWolf]

The handle is 0x0

logcat.txt

[MikuAuahDark]

Ok you probably also want to log the result of SDL_GetError() when the handle is nullptr.

[Aurelius7309]

SDL_GetError() yields the following: Error: Failed loading /data/app/~~x8g5rTTI8IfSiobVEau_Iw==/systems.shorty.lmm-mNh7Ap-UqS_2FWzd5zzBzA==/lib/arm64/https.so: dlopen failed: library "/data/app/~~x8g5rTTI8IfSiobVEau_Iw==/systems.shorty.lmm-mNh7Ap-UqS_2FWzd5zzBzA==/lib/arm64/https.so" not found

[MikuAuahDark]

Hmm, that can only mean 1 thing: The https.so doesn't get extracted together when installing the APK.

If you keep the debuggable="true" in the manifest while building release APK, and use run-as systems.shorty.lmm through ADB shell to inspect the /data/app/~~x8g5rTTI8IfSiobVEau_Iw==/systems.shorty.lmm-mNh7Ap-UqS_2FWzd5zzBzA==/lib/arm64 folder, is https.so is there or?

[Aurelius7309]

That unfortunately has me running in circles. The library works when debug symbols are attached; this is also true when building release with debuggable="true". Meaning https.so is present as expected, though this is unhelpful for the issue in release builds