question

Justin Griep avatar image
Justin Griep asked

Addressing APK is not 64-bit compliant

I have been wrestling for a good number of days with the validation problem:

Your APK is not 64-bit compliant. This may lead to some devices not being supported.

In my case, I have a Microsoft Xamarin application with a hybrid package built for both "armeabi-v7a" and "arm64-v8a". This seems to work fine with Android and Google Play, just failing this validation for Amazon Fire. It looks like others have had this same issue for example with Unity and that the validation is pretty picky.

When I do an APK build that is 32-bit only (armeabi-v7a) there is no validation error and it shows all the Fire Tablets I would like to support.

However, the support docs state "Some devices no longer support 32-bit apps...". Does this include any Fire Tablets?

If this is just other non-Amazon devices, I am inclined to just stay 32-bit only on the Amazon App Store.

amazon appstoreapp submission and updates
10 |5000

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

1 Answer

Justin Griep avatar image
Justin Griep answered

In the end, the only way I could find to get published to the store was to do 32-bit only (armeabi-v7a) which works fine with all of the Fire devices. In my case, this also was important for IAP support where the plugin we are using binds to a file, "libAmazonIapV2Bridge.so" that is only available in 32-bit anyway. So the discrepancy may have even been caused by this Amazon provided plugin.

10 |5000

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.