16KB Page Size Unsupported

[MaxDeh2203]

When building an APK with V3.0.7, I still encounter issues with 16KB page size alignment.

I created an empty project with Unity Version 6000.0.71f1 and let Unity build for Android. The resulting build encounters no errors:

Afterwards, I added the Mapbox package to the project as detailed in the installation description.

First, the build does not succeed due to Gradle issues:

`
What went wrong:

Execution failed for task ":launcher:mergeDebugNativeLibs".

A failure occurred while executing com.android.build.gradle.internal.tasks.MergeNativeLibsTask$MergeNativeLibsTaskWorkAction

2 files found with path "lib/arm64-v8a/libc++_shared.so" from inputs:

  - PROJECTPATH/Library/Bee/Android/Prj/IL2CPP/Gradle/unityLibrary/build/intermediates/library_jni/debug/copyDebugJniLibsProjectOnly/jni/arm64-v8a/libc++_shared.so

  - GRADLEPATH/.gradle/caches/8.13/transforms/2e6a333e48c2db01e073a24617af2b10/transformed/jetified-common-ndk27-24.10.0/jni/arm64-v8a/libc++_shared.so

 If you are using jniLibs and CMake IMPORTED targets, see

 https://developer.android.com/r/tools/jniLibs-vs-imported-targets

`

If I tell Gradle to pick the first version it gets via the "packaging" attribute in the gradle launcher template, the build succeeds, but the resulting APK is not 16KB aligned:

[brnkhy]

Hey @MaxDeh2203;
This 16kb issue still confuses me to be honest. I did my checks using the script here; https://developer.android.com/guide/practices/page-sizes#elf-alignment
and everything looked fine using that script. can you give it a shot and share what it says?

[MaxDeh2203]

Thanks for the reply @brnkhy !

I have run the script, it shows that the libraries it finds are properly aligned.

ELF alignment
/var/folders/0g/vv61d34d4_79yvplssvv0nm80000gn/T/demo_with_mapbox2_out_XXXXX.vdL3i7ocSp/lib/arm64-v8a/libmain.so: \e[32mALIGNED\e[0m (214)
/var/folders/0g/vv61d34d4_79yvplssvv0nm80000gn/T/demo_with_mapbox2_out_XXXXX.vdL3i7ocSp/lib/arm64-v8a/libmapbox-common.so: \e[32mALIGNED\e[0m (214)
/var/folders/0g/vv61d34d4_79yvplssvv0nm80000gn/T/demo_with_mapbox2_out_XXXXX.vdL3i7ocSp/lib/arm64-v8a/libil2cpp.so: \e[32mALIGNED\e[0m (214)
/var/folders/0g/vv61d34d4_79yvplssvv0nm80000gn/T/demo_with_mapbox2_out_XXXXX.vdL3i7ocSp/lib/arm64-v8a/libgame.so: \e[32mALIGNED\e[0m (214)
/var/folders/0g/vv61d34d4_79yvplssvv0nm80000gn/T/demo_with_mapbox2_out_XXXXX.vdL3i7ocSp/lib/arm64-v8a/libunity.so: \e[32mALIGNED\e[0m (214)
/var/folders/0g/vv61d34d4_79yvplssvv0nm80000gn/T/demo_with_mapbox2_out_XXXXX.vdL3i7ocSp/lib/arm64-v8a/libc++_shared.so: \e[32mALIGNED\e[0m (214)
/var/folders/0g/vv61d34d4_79yvplssvv0nm80000gn/T/demo_with_mapbox2_out_XXXXX.vdL3i7ocSp/lib/arm64-v8a/libsqlite3.so: \e[32mALIGNED\e[0m (216)
/var/folders/0g/vv61d34d4_79yvplssvv0nm80000gn/T/demo_with_mapbox2_out_XXXXX.vdL3i7ocSp/lib/arm64-v8a/lib_burst_generated.so: \e[32mALIGNED\e[0m (214)
ELF Verification Successful

However, the check_elf_alignment.sh script does not seem to check libsqlite3 (which is the cause for the warning when analyzing the APK in Android Studio).

[MaxDeh2203]

I have a suspicion that the Newtonsoft JSON Package dependency is an issue. The Mapbox Package 3.0.7. uses Newtonsoft 3.2.2. as a dependency, which hasn't been updated since 2022ish.

[brnkhy]

@MaxDeh2203

/var/folders/0g/vv61d34d4_79yvplssvv0nm80000gn/T/demo_with_mapbox2_out_XXXXX.vdL3i7ocSp/lib/arm64-v8a/libsqlite3.so: \e[32mALIGNED\e[0m (216)

isn't this the sqlite library?
for what it's worth, I checked with Claude and it says v8a sqlite library is 64kb aligned so it should be good for 16kb as well.

[MaxDeh2203]

@brnkhy Ah you're right, I overlooked it in the console output produced by the shell script.

In that case I'm not sure why Android Studio shows the warning.

I'll attempt to send the build through the publishing pipeline and see if Google complains at any point to produce a definitive answer. I'll update here if I get any results.

[brnkhy]

In that case I'm not sure why Android Studio shows the warning.

I'm really lost on that one as well but as you suggested, I think trying to publish a build is probably the only guaranteed way we can figure this out; I'm very curious about this as well.

[dashcambike]

FWIW i have deployed on Android with mapbox unity v3 without alignment issues, so it can be done. I don't recall doing anything specific for this library (though several other dependencies had issues). Let me know if there's something I can test on my end to see the differences between what I have and what you're seeing.

[tomCarnevale]

We are seeing a similar issue with the sqlite3 library. It wasn't flagged by the developer console (other libraries from other packages were, which is why I'm checking). Hoping it goes through as well, will update with results.

[MaxDeh2203]

Just a quick follow-up @tomCarnevale @brnkhy:

Publishing on the Play Store did in fact work without issues, it seems to be a false flag in Android Studio.

[absences]

https://github.com/absences/sqlite_android_lib
use github workflow to build sqllite android lib