targetSdkVersion = 35 shows warning for missing 16 KB page size support

[ankit2saurabh]

When updating targetSdkVersion to 35, our app displays the following warning on some newer Android devices:

This app isn’t 16 KB compatible. ELF alignment check failed.
This app will be run using page size compatible mode. For best compatibility, please recompile the application with 16 KB support.
For more information, see https://developer.android.com/16kb-page-size

[true-hamid]

We are also facing this issue. If its not supported, google will block our app, and we might have to drop huawei completely

[llitfkitfk]

@hmscore/react-native-hms-location not support 16kb page

[eliot-ye]

same issue, i get this warning

APK app-debug.apk is not compatible with 16 KB devices. Some libraries have LOAD segments not aligned at 16 KB boundaries:
lib/arm64-v8a/libTransform.so
lib/x86_64/libucs-credential.so
Starting November 1st, 2025, all new apps and updates to existing apps submitted to Google Play and targeting Android 15+ devices must support 16 KB page sizes. For more information about compatibility with 16 KB devices, visit developer.android.com/16kb-page-size.

[alpersaliksetcard]

We are also facing this issue. If its not supported, google will block our app, and we might have to drop huawei completely

why are you using this package for google play build. We produce different build for huawei app gallery and google play console. we don't include huawei packages for google play builds. you can use android flavors to seperate builds.

[eliot-ye]

We are also facing this issue. If its not supported, google will block our app, and we might have to drop huawei completely

why are you using this package for google play build. We produce different build for huawei app gallery and google play console. we don't include huawei packages for google play builds. you can use android flavors to seperate builds.

@alpersaliksetcard How do you control the packaging of different target versions containing different SDKs?