question

Gumdrops72 avatar image
Gumdrops72 asked ·

64-bit support issue

We are trying to upload an apk which has 64-bit support (ARM64 architecture supported) and it's telling us we don't have 64-bit support.

This appears to be a new issue as APK's we uploaded last week didn't have this problem. Can someone please advise us on how to fix or or resolve this.

We are using Unity 2017

thank you!

amazon developer portal
2 comments
10 |2000 characters needed characters left characters exceeded

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

Same problem here. App has always supported 64-bit, and nothing's changed on our end.

App is compiled with Android Studio/Cocos and passes Google Play validation for 64-bit just fine.

0 Likes 0 ·

Hi there, please also see the following thread where I answered a similar question:
https://forums.developer.amazon.com/questions/239643/64-bit-issue-uploading-apk-to-amazon-using-unity-2.html

0 Likes 0 ·
CdrJameson avatar image
CdrJameson answered ·

I have a response from support...

 
               
For an app to be published on 64-bit devices, the APK should contain 64-bit library folder (lib\arm64-v8a), and it should contain *all* the libraries that are present in 32-bit library folder.
If developers want to target these devices, then they should keep the same set of libraries in both 32-bit and 64-bit library folders, otherwise the app would get published only on 32-bit devices as usual.

If the APK doesn't have 64-bit library folder at all, the check is not performed.

Only if the folder for 64-bit is present and it does not contain all the same libraries as 32-bit, then this check is performed and the error message is displayed.

This change was introduced on May 7th, so with the same build, the developer will see this behaviour now.

We are working on improving the messaging and will be providing a "Learn More" link.
If we completely remove the check it is possible that some apps may go into publishing/live and then fail during installation/runtime.

For any app:If the app doesn't want to target the latest 64-bit Amazon devices, then please delete the 64-bit library folder.

Otherwise, ensure that both 32-bit and 64-bit lib folders are present and have the same content.

Developers can target Fire HD 10 (11th Gen) devices only if:
- libs in 64-bit and 32-bit are equivalent (same names and count)- No 64-bit libs and folder
- This will use 32-bit mode for apps as Fire HD 10 (11th Gen) is hybrid device.

If neither condition is met, developer will still be able to submit, but not for Fire HD 10 (11th Gen) devices.

...So I think this explains the problem I was having.

It's the wrong assumption that the 32-bit and 64-bit folders have to have the same named libraries in them.

In my app there's a supplementary library that is needed to patch over a problem that only happens on 32-bit, and so only appears in the 32-bit folder. There's no copy of it in the 64-bit folder because it's not needed on 64-bit.

I shall put a couple of empty files with the appropriate names in the 64-bit folder and see if I have more luck on resubmission.

10 |2000 characters needed characters left characters exceeded

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

Gumdrops72 avatar image
Gumdrops72 answered ·

Does Amazon Developer support have any answers on this? We've contacted them, and have no support or answers on how to fix this issue. Please advise soon as we'd like to continue updating our apps.

10 |2000 characters needed characters left characters exceeded

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