[Help Wanted]: 16KB page size not supported
Required Reading
- [x] Confirmed
Plugin Version
7.1.0
Mobile operating-system(s)
- [ ] iOS
- [x] Android
Device Manufacturer(s) and Model(s)
All Android devices
Device operating-systems(s)
Android 15
What do you require assistance about?
When uploading the app to the android store I'm getting the below message:
Libraries that do not support 16 KB: base/lib/arm64-v8a/libTransform.so base/lib/x86_64/libucs-credential.so
I run the following commands and receive the following output:
Command: Get-ChildItem -Recurse "$env:USERPROFILE.gradle\caches" -Filter "libTransform.so" Output: Directory: C:\Users\user1.gradle\caches\8.10.2\transforms\abcd\transformed*core-2.9.0.300*\jni\arm64-v8a Mode LastWriteTime Length Name ---- ------------- ------ ---- -a---- 17/03/2025 11:18 AM 9928 libTransform.so Directory: C:\Users\user1.gradle\caches\8.10.2\transforms\abcd\transformed*core-2.9.0.300*\jni\armeabi-v7a Mode LastWriteTime Length Name ---- ------------- ------ ---- -a---- 17/03/2025 11:18 AM 17960 libTransform.so
Command: Get-ChildItem -Recurse "$env:USERPROFILE.gradle\caches" -Filter "libucs-credential.so" Output: Directory: C:\Users\user1.gradle\caches\8.10.2\transforms\abc\transformed*ucs-credential-developers-1.0.3.314*\jni\x86 Mode LastWriteTime Length Name---- ------------- ------ ---- -a---- 17/03/2025 11:18 AM 429836 libucs-credential.so Directory: C:\Users\user1.gradle\caches\8.10.2\transforms\abc\transformed*ucs-credential-developers-1.0.3.314*\jni\x86_64 Mode LastWriteTime Length Name ---- ------------- ------ ---- -a---- 17/03/2025 11:18 AM 489400 libucs-credential.so
I then run the following to see all dependencies ./gradlew app:dependencies
This gives me a massive list with all. If I search up either of core-2.9.0.300, ucs-credential-developers-1.0.3.314 it points me back to the com.huawei.hms package. (com.huawei.hms.LocationLiteSdk:core:2.9.0.300, com.huawei.hms:ucs-credential-developers:1.0.3.314)
Following up the dependency tree it points back to transistorsoft/capacitor-background-geolocation
I have tried uninstalling and reinstalling, deleting node_modules but I still get the same error when uploading it to the android store
Thanks Chris
[Optional] Plugin Code and/or Config
[Optional] Relevant log output
I'd also really love a fix for this.
I know all about it.
This month I’ll work on it.
We are also blocked by this issue, and it's becoming critical with the looming November 1st Google Play deadline. We would greatly appreciate an update on the timeline for a fix.
Have you seen the CHANGELOG?
Have you seen the CHANGELOG?
Thank you for pointing me to the CHANGELOG. I can see the fix has been released. The fact that this issue was still open was what caused my confusion.
I’m waiting for people to confirm.
You should subscribe yourself to this repo so you get notified of changes.
Just set hmsLocationVersion to "6.16.0.302" in variables.gradle. Also keep in mind you must set plugin version to exact "7.1.0" in package.json because Huawei support been removed in 7.2.0 and above.
could confirm that with 7.2 the problem is fixed
@ximex Of course, I apologize for the misunderstanding. My previous comment only applies to using the plugin with Huawei devices.
If you don't need support for Huawei, version >= "7.2.0" will solve your problem, as support for Huawei has been removed in this version.
If you need support for Huawei devices, you must set the exact version "7.1.0" of the plugin and set the hmsLocationVersion variable in variables.gradle to version "6.16.0.302", in which this problem has already been fixed by Huawei. For those who need Huawei support, we will see if and when @christocracy will bring back support.
When it comes back, it'll be implemented in different way, not requiring users to always import the Huawei dependencies.
This will require some serious engineering with srcSets configuration, a custom proxy layer within the SDK to wrap significant portions of the play-services location, geofencing and motion APIs, route calls to hms/gms and a separate build flavour for the HMS version.
This issue is stale because it has been open for 30 days with no activity.
This issue was closed because it has been inactive for 14 days since being marked as stale.