We've updated to the latest version of the Barcode Plugin but the generated apk still contains a .so which doesn't support 16K pagination. We can confirm that the issue comes from the plugin since we've removed all other references and built the test package with the latest MBAS 12.
The flagged library is libbarhopper_v3.so.
Before updating to the latest version, there are two libraries flagged: libbarhopper_v3.so and libimage_processing_util_jni.so. The later one is 16K now but the former one is still not.Can we do something about it? We do have a deadline from Google to update our application before May 2026.
Hey @Binh Cao, thanks for posting this. Can you please clarify what you mean exactly when you say "the generated apk still contains a .so which doesn't support 16K pagination"?
Where are you getting this information from? Is Google Play giving you this warning? Are you seeing this information from Android Studio? Are you running a script to check if the libraries are 16KB-aligned?
At least for the latter, it's worth stating that for libbarhopper_v3.so you'll get 16KB-unaligned for armeabi-v7a and x86 architectures. But, as the documentation states (point 3), they only need to be 16KB-aligned for arm64-v8a and x86_64. So this should not result in any warning in Play Store. We've tested submitting apps to the Play Store ourselves and got no warning with the latest plugin version.
Hope it helps!
Hi @Pedro Gustavo Bilro Thank you very much for the quick and very helpful response.
We are running a script with llvm-readelf to check our apk. We haven't submitted the new version to Google Play yet.
I've looked at the result from the script and you're right that the warnings only come from the armeabi-v7a and x86. So, it seems that we are safe to submit our new package to Google.