Successful Unity aab build not compliant with the Google Play 64-bit requirement

Unity Engine
,
1

Hi,

I’m switching from APK to AAB.

With a successful Unity aab build, following these guidelines:

I’m still getting the following error in the google Play Console:

“This release is not compliant with the Google Play 64-bit requirement. The following APKs or App Bundles are available to 64-bit devices, but they only have 32-bit native code”

  1. I have both ARM7, ARM64 and x86 architectures set.
  2. When I open the .aab in an archive viewer, the lib folder has all of the .so’s for both arm64-v8a and armabi-v7a.
  3. Using IL2CPP, .NET 4.x
  4. Unity 2019.1.9f1
  5. Android Studio 3.4.2
  6. SDK Platform: 9.0(28);Platform-Tools: 29.0.2, tools:26.1.1 (I have tried builds with the Unity hub delivered SDK or with my downloaded copy, I still get the same error in the google play console)
  7. NDK: 16b

Is this a Unity problem?
Or Google bug ?(android gradle plugin - Unity aab not compliant with the Google Play 64-bit requirement - Stack Overflow)
Or is there some other step I’m missing?

3 Likes
2

We’ve been doing the same process for the past 20+ builds without issue, but this morning our build is getting rejected by Google with the same error. Not sure if this is a Google problem?

1 Like
3

Have the same problem, checked that all libraries have 64-bit counterparts using APK Analyzer, but still can’t upload the app (to beta track).

1 Like
4

Same problem here: Since today my app bundle gets rejected from google play and it used to work for the last 5 builds.

I’m using
Unity 2019.2.0f1,
IL2CPP,
ARM7, ARM64 and x86,
.NET Standard 2.0,
Master-Release

5

This is likely caused by x86 (32bit) not having a 64bit counterpart.

Quick fix for us was to remove x84 support. But this means a bunch of people who have the x86version of the app are goners.

4 Likes
6

Same here, just happened for me too.
over 50 successfull builds and uploads.
.NET 4.X equivalent
IL2CPP
.NET Standard 2.0
Release
ARM7,ARM64,X86
Any fixes yet?

2 Likes
7

I uploaded the same build that was accepted on Friday into internal track to beta track today and it failed. Must be something wrong from Google’s side.

1 Like
8

I even went on google dev live chat and was (as expected) just bombarded with copy-paste links about switching to 64 bit code since 01 AUG.

It now seems it’s a problem on their end.

9

I have the same problem.

10

Do you guy’s build support x86 64bit?

11

Someone on reddit stated that removing x86 support fixed the issue, however i can’t see that being a good idea in the long run.
https://www.reddit.com/r/Unity3D/comments/csia5v/android_app_bundle_not_including_64bit_native/

2 Likes
12

Removing it does work (as mrm83 already said).

3 Likes
13

Would this not stop the app from working on an x86 devices? I dont know enough about this stuff to understand it all.

1 Like
14

I am not entirely sure either, I don’t have an x86 device at hand to test. I will get back to you after getting more information or finding a compatible device.

15

Anyone have any other workarounds yet or can confirm that disabling x86 won’t have any impact on user acquisition?

16

x86 is used by less than 0.4% of all Android devices, so it shouldn’t have any real impact.

You may probably already noticed but in 2019.2 x86 target is marked as deprecated, in 2019.3 it will be removed completely.

4873088--469874--AndroidCPUStats.jpg
4873088--469874--AndroidCPUStats.jpg784×592 44.9 KB

7 Likes
17

Great thanks for the clarification.
Still not sure why only today this error appeared on Google console.

1 Like
18

good night, I have the same problem, I can’t update my app, but I remove the x86, and I get another warning.

1 Like
19

I filed a bug report with the respective aab with Google. They’re on it. Keep you guys informed.

4 Likes
20

Same problem here.

Please keep in mind much developer are not able to upload aab (app bundle) because of incompability with some library their have to build an apk.

It should also work with apk files.