This release is not compliant with the Google Play 64-bit requirement

(Deprecated) Help: ExpoKit
1

Warning in Google Play:

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.

From August 1, 2019 all releases must be compliant with the Google Play 64-bit requirement.

Include 64-bit and 32-bit native code in your app. Use the Android App Bundle publishing format to automatically ensure that each device architecture receives only the native code it needs. This avoids increasing the overall size of your app.

How to fix this problem?

1 Like
2
1 Like
3

@adamjnav Which left panel do you mean?

4

As far as I understood, this problem was fixed in react-native 0.59, however, expo/ expoKit is not supporting react-native 0.59 now, is that correct?

5

We are experiencing the exact same issue,
any solutions ?

6

I think the solution is to wait once expo will start support react-native 59.0 and after that update expo and react native

7

The message in Play Console is not blocking your release. It’s a warning message but you are still able to push out .apks that are not 64-bit as Google’s deadline on this is August 1st, 2019.

8

@adamjnav so? I know, I can read. That was not my question. My question is how to fix this warning? I don’t want to be blocked 1st of August of this error, meaning that I want to fix it now.

9

Ah, my bad. As you mentioned, you’ll have to wait until we add 64-bit support which will be with SDK34 or SDK35’s release.

1 Like
10

Omg, I though it would be available in SDK 33.

11

You will add it before 1st august?

12

Yeah, we’ll definitely have support rolled out before then. We will try to give developers as much time as possible before the deadline.

13

Thanks for your great work.

14

+1 following.
Thanks for the great work team.

15

I am using SDK 30. if SDK is updated, am I going to have to re-create the project and separate the project and write the code again and receive the module again?

16

Is there a place where you have a timeline of when you plan to release those versions?

SDK33 is not out yet and you’re saying that it might be added in SDK 34/35 which I/we have no idea when it’s going to be released.

17

No, we don’t have a timeline for this. All I can say is that we’ll make sure that 64-bit support is out before the deadline so that no Expo developer’s release cycle is inhibited.

18

Once the new version is released, and will my code be OK if I update my SDK?

19

This seems pretty important to have a timeline for, especially if the migration of existing Expo apps takes a significant amount of work.

20

It won’t require any extensive migration. Only new submissions after Aug. 1st will be required to be 64-bit and that would only require building a new binary once we’ve updated the android builders.

1 Like