[Android App Bundle] What's happening with Google Play? Can not publish my APP

this is in the last beta release 292.8 for developer version, now this does not stop you to publish your application in any way.

Quote from Fernando

this is in the last beta release 292.8 for developer version, now this does not stop you to publish your application in any way.

Got the same damn message - Use the Android App Bundle to automatically optimize
WHAT SHOULD I DO?)

Good morning,

I still have this message:

Quote from Guilherme

What should I do?Please login to see this attachment.Please login to see this attachment.

But I don't understand how to solve it.
does anyone know how to solve it?

Tnk1000

(As far as I understand, Fernando please correct me if I'm wrong)

When you build an APK file with Fusion (or anything else), it contains both 32 and 64-bit library files as well as resources for any device resolution. This is OK, though Google displays this "warning" message. You can ignore this message. If you want to remove it you have to create an App Bundle instead, there is a new build type for this in the build 292, Developer version.

When you build an App Bundle, Google builds the APK file at the moment the user installs your app, and puts inside this APK only the libraries and resources the user's device needs

Please login to see this link.

Thank Yves you very much for the explanation. Now I try to do app bundles and we'll see what happens.
-----------------------
I managed to do app bundles, but it won't let me do the rollout .... any solution?

Tnk1000

Please login to see this attachment.

The app optimization size is just a warning at the moment that we can ignore.

You have to use Google to sign your keystore file to use app bundles -if you opt-out of that, then you still have to use a single .apk

And also with Fusion, and only with Fusion, you save so little i.t.o. actual space by having an app bundle that it's more trouble than it's worth.

Quote from casa

Thank Yves you very much for the explanation. Now I try to do app bundles and we'll see what happens.
-----------------------
I managed to do app bundles, but it won't let me do the rollout .... any solution?

Tnk1000

Please login to see this attachment.

did you also upload the certificate that this application use? seems missing.

Please login to see this attachment.

good morning,

maybe i did...

Now that Google Play no longer accepts Fusion built apk's after 1st August 2019, even though they're updated with 64 bit code. It seems we have to use app bundles instead. Is this correct and can anyone give any steps to take to create and upload an encrypted keystore file to Google's signing service?

I just built an .apk on 292.11 to check this and uploaded it on Google Play.

It's still accepting them - but I did get this message:

Warning
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: 3.

From February 1, 2020 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. Learn More

However, it would allow me to update (I cancelled, as this was a test - but the button: Start roll-out to production was enabled.)

Oddly though the update showed I was using GLS 1.1 - when I had GL 3.0 selected in Fusion.

I am NOT using Google certificate signing.
I am NOT using App Bundles.

So if Google isn't allowing you to update, there must be a different problem. (Perhaps your version number?)

Unfortunately I get the same message but my date for here in the UK is:

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

So I just get a big red error message and you cannot 'roll out' the apk.

I uploaded apk's in July with the latest updates of Fusion etc., and it said they were 64 bit compliant so didn't think anymore of it. I didn't get a message saying they were not compliant with the 'Google 64 bit requirement'. So typical Google have moved the goal posts again.

Plus Google is so hypocritical about the size of your app when mine are 1.5 or 2 MB and they're bloatware consumes most of Android's drive space.

Of course the reason they are targeting independant developers is they don't want us anymore unless we're making a decent amount for them. With the rubbish GDPR laws that Europe has now, which incidentally do not protect the user in any way, Google now wants only software companies and big independant names so they can push any data law suits onto them.

So can anyone help with the app bundles certificate/keystore how to?

Looking at the .apk in Android Studio - the 64 bit libraries are there - but there's nothing in the manifest to indicate that.

There's been no response on this issue - it was first reported on the 9th of July: Please login to see this link.

Please can we have some feedback on what is happening here? It shouldn't be necessary for us to build app bundles (yet).

[MENTION=32521]Jann[/MENTION]ete5

this have been answered in teh past the libraries are there and are used by those devices are 64 bits and teh packaged is done at it shoudl since it done by gradle or ANT in teh past

can you point, what do you mean with

Quote

but there's nothing in the manifest to indicate that.

Google Play isn't recognizing the 64 bit. It's telling us that our apps are not 64 bit compliant. It's doing so immediately on loading the .apk that is built with 292.11

It means we're stuck. We're forced to use an app bundle or we can't update our apps.

yes I will check

but what shoudl be added to the manifest, Where did you read this?

The manifest part you can ignore - because it's an assumption on my part - that if the bundles work, then clearly there is nothing wrong with your libraries - only something like a missing entry in the manifest.

I had mentioned it after seeing this:

Caution: if an app exposes an api to other apps that can be either 32 or 64 bit, the app must have the android: multiarch property set to a value of true within its manifest to avoid potential errors.

It's a heading on the search - but when you open the actual document I couldn't find more info about it Please login to see this link.

After posting that, I compared the Fusion manifest to a Godot manifest that is 64 bit compliant and couldn't find anything further. (Godot apk built by me on same pc, using same certificate etc.)

However, Android studio did give me 2 errors on the Fusion manifest:

Missing Android XML namespace Most Android views have attributes in the Android namespace. When referencing these attributes you must include the namespace prefix, or your attribute will be interpreted by aapt as just a custom attribute. Similarly, in manifest files, nearly all attributes should be in the android:

Target SDK attribute is not targeting latest version When your application runs on a version of Android that is more recent than your targetSdkVersion specifies that it has been tested with, various compatibility modes kick in. This ensures that your application continues to work, but it may look out of place. For example, if the targetSdkVersion is less than 14, your app may get an option button in the UI. To fix this issue, set the targetSdkVersion to the highest available value. Then test your app to make sure everything works correctly. You may want to consult the compatibility notes to see what changes apply to each version you are adding support for: Please login to see this link. as well as follow this guide: Please login to see this link. Issue id: OldTargetApi

you know godot packs assets and some few code right is base mostly in pre built libs, but fusion is based in java and partial code in C.

Back to 64 bits application please always track google android pages like this one Please login to see this link.

if you do teh test mentioned there you will see that the apk is 64 bits

Please login to see this attachment.

if you execute this command and give no error you are OK

Quote

C:\Users\XXXXX\Desktop\Old MFAs>adb install --abi arm64-v8a IgnorebatteryOptimizations.apk
Performing Streamed Install
Success

I am testing bundle and seems to be a problem with signing in the google page checking if is working or not (google).

Quote from Fernando

I am testing bundle and seems to be a problem with signing in the google page checking if is working or not (google).

It's not the bundle we're having a problem with - it's the standalone .apk

I can see that the 64-bit libraries are there - but Google Play's computer is not recognising them for whatever reason.