epic: fix Android 16 KB compatibility

[ovitrif]

Goal

Ship Bitkit without Android's page-size compatibility alert on a fresh 16 KB installation.

Proven root cause

A clean uninstall/install of mainnetDebug on Android 17/API 37 with PAGE_SIZE=16384 changed only AndroidX DataStore from 1.2.0 to 1.2.1. That single version change cleared the complete compatibility alert.

Every other native dependency remained unchanged. The alert's Unknown error entries for those libraries were collateral compatibility-mode reporting, not evidence of separate per-library 16 KB failures.

Active scope

• fix: update DataStore for 16 KB compatibility #1103 tracks the DataStore correction and acceptance criteria.
• fix: update DataStore for 16 KB compatibility #1107 implements the DataStore 1.2.1 update.

Historical diagnostic context

The producer NDK mismatch and the stricter RELRO-end alignment heuristic were useful diagnostics while investigating the alert. The fresh-install result established that neither was a causal requirement for this product fix.

Acceptance criteria

• fix: update DataStore for 16 KB compatibility #1107 receives approval and merges.
• A clean uninstall/install on Android 17/API 37 with PAGE_SIZE=16384 reaches Bitkit without the compatibility alert; the captured runtime result reports pageSizeCompat=0.
• The implementation passes the repository's compile, test, lint, dependency-resolution, and hosted CI/E2E checks.

[pwltr]

Update from fresh release artifact validation:

Built/check artifacts:

• app/build/outputs/apk/mainnet/release/bitkit-mainnet-release-184-*.apk
• app/build/outputs/bundle/mainnetRelease/bitkit-mainnet-release-184.aab

Resolved in the fresh artifacts:

• libdatastore_shared_counter.so no longer fails after bumping androidx.datastore:datastore-preferences to 1.2.1.
• libpaykit.so no longer fails in the fresh release APK/AAB payload.
• libvss_rust_client_ffi.so no longer fails in the fresh release APK/AAB payload.

Still failing in the Play Store AAB:

• libandroidx.graphics.path.so: arm64-v8a RELRO end=0x6000
• libsurface_util_jni.so: arm64-v8a RELRO end=0x5000

Additional APK-only/local split finding:

• x86_64 APK also fails libbarhopper_v3.so RELRO end=0x59b000. The mainnet release AAB currently reports only the two arm64 failures above.

Notes:

• Tried overriding androidx.graphics:graphics-path to 1.1.0; RELRO still failed, so not kept.
• Tried CameraX 1.6.1; libsurface_util_jni.so still failed, so not kept.
• Added scripts/check-16kb-compat.sh and wired it into local and CI release validation so future release APK/AAB artifacts fail before upload if any 16 KB compatibility issue remains.

[pwltr]

Correction after re-checking Google's official 16 KB page-size guidance and testing on an Android 17 emulator.

The previous RELRO end-address failures were from an over-strict local heuristic, not from Google's documented compatibility check. Google's docs require ELF LOAD segment alignment of at least 2**14 / 0x4000, APK zip alignment via zipalign -P 16, and GNU_RELRO presence as a security flag check. They do not require the GNU_RELRO end address to be 16 KB aligned.

After updating scripts/check-16kb-compat.sh to match the documented checks, the fresh release artifacts pass:

• bitkit-mainnet-release-184.aab: PASS native 16 KB checks (10 libraries)
• bitkit-mainnet-release-184-arm64-v8a.apk: PASS zipalign; PASS native 16 KB checks (10 libraries)
• bitkit-mainnet-release-184-universal.apk: PASS zipalign; PASS native 16 KB checks (10 libraries)
• bitkit-mainnet-release-184-x86_64.apk: PASS zipalign; PASS native 16 KB checks (10 libraries)

I also installed and launched bitkit-mainnet-release-184-arm64-v8a.apk on an Android 17 emulator with SDK 37 and PAGE_SIZE=16384. The app launched successfully, the UI hierarchy showed Bitkit's Terms screen rather than an Android compatibility warning dialog, and logcat did not show any 16 KB / RELRO / linker compatibility warnings after launch.

Conclusion: with fresh 184 artifacts, Google's documented static checks, and runtime launch on Android 17 / 16 KB pages, this does not appear to block Play Store release.

[ovitrif]

Gave this another try, I simply built using Android Studio the latest commit on master using mainnetDebug and mainnetRelease build variants targeting my Pixel phone with Android 17 Beta installed.

Below images are screenshots of scrcpy app doing physical device mirroring to my machine, took right after the app was opened after Android Studio installed it:

mainnetDebug	mainnetRelease

Conclusion from my side: might've been either a debug build-only issue or appearing on release builds of previous patch releases which were not incorporating all recent changes since June, I think it's safe to close it and reopen if we encounter related issues.

Thanks for your investigation @pwltr 🙏🏻 .

[pwltr]

I can reproduce on mainnetDebug build on a Android 17 16KB page size emulator.

[piotr-iohk]

Note that this started to appear for 2.3.2 in play store:

[piotr-iohk]

Reopening. The warnings are also visible in Play for 2.4.0.