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

292.12 Latest Error building an APP Bundle

Starting a Gradle Daemon, 1 incompatible Daemon could not be reused, use --status for details

> Configure project :app
WARNING: The option setting 'android.overridePathCheck=true' is experimental and unsupported.
The current default is 'false'.

> Task :app:preBuild UP-TO-DATE
> Task :app:preReleaseBuild
> Task :app:compileReleaseRenderscript
> Task :app:generateReleaseResValues
> Task :app:generateReleaseResources
> Task :app:mergeReleaseResources
> Task :app:checkReleaseManifest
> Task :app:createReleaseCompatibleScreenManifests
> Task :app:mainApkListPersistenceRelease
> Task :app:processReleaseManifest
> Task :app:bundleReleaseResources
> Task :app:mergeExtDexRelease
> Task :app:compileReleaseAidl NO-SOURCE
> Task :app:generateReleaseBuildConfig
> Task :app:prepareLintJar
> Task :app:generateReleaseSources
> Task :app:javaPreCompileRelease
> Task :app:processReleaseResources

> Task :app:compileReleaseJavaWithJavac
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.

> Task :app:transformClassesWithDexBuilderForRelease
> Task :app:mergeDexRelease
> Task :app:mergeReleaseShaders
> Task :app:compileReleaseShaders
> Task :app:generateReleaseAssets
> Task :app:mergeReleaseAssets
> Task :app:compileReleaseNdk NO-SOURCE
> Task :app:mergeReleaseJniLibFolders
> Task :app:transformNativeLibsWithMergeJniLibsForRelease
> Task :app:processReleaseJavaRes NO-SOURCE
> Task :app:transformResourcesWithMergeJavaResForRelease
> Task :app:buildReleasePreBundle
> Task :app:validateSigningRelease
> Task :app:signingConfigWriterRelease
> Task :app:packageReleaseBundle FAILED

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':app:packageReleaseBundle'.
> java.util.concurrent.ExecutionException: com.android.tools.build.bundletool.exceptions.BundleFileTypesException$FileUsesReservedNameException: File 'root/res/values-v9/obb_styles.xml' uses reserved file or directory name 'res'.

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

* Get more help at Please login to see this link.

Deprecated Gradle features were used in this build, making it incompatible with Gradle 6.0.
Use '--warning-mode all' to show the individual deprecation warnings.
See Please login to see this link.

BUILD FAILED in 1m 31s
27 actionable tasks: 27 executed

Quote from Rickyvb

292.12 is located where? I tried using the update feature, to no avail. I tried Passport to no avail? Is there a post or link?

For anyone else searching for the download link for 292.12 it's in the Owner's Lounge Download Links in the Beta section

Please login to see this link.

Quote from Rickyvb

Never mind, it was hidden under other links. Come on clickteam. Can you put the beta versions under Beta Versions, within the community passport?

Yeah, it's in the passport now, sorry, for some reason there was no entry for 2.5 beta versions.

PS: the Product Owner's Lounge forum is in the Support Forums section like Fusion 2.5, it contains the archive of all recent download files for each product.

Quote from Yves

Yeah, it's in the passport now, sorry, for some reason there was no entry for 2.5 beta versions.

PS: the Product Owner's Lounge forum is in the Support Forums section like Fusion 2.5, it contains the archive of all recent download files for each product.

Thanks.

Any Solution on the Latest Error I am getting with BUILD 292.12?

Again, 292.11 had no issue at all building an .apk that works beautifully with AMAZON APP Store. However, Building an App Bundle, is still showing errors.

Maybe it is me? Is there a tutorial on Building and app Bundle somewhere? All I have been doing is Changing the output from my working .APKs to .AAB. Which shows the error I posted above.

I assume it is me, because if I simply make a Blank .aab application. It builds fine!

Thanks in advance...

Quote from Rickyvb

Thanks.

Any Solution on the Latest Error I am getting with BUILD 292.12?

Again, 292.11 had no issue at all building an .apk that works beautifully with AMAZON APP Store. However, Building an App Bundle, is still showing errors.

Maybe it is me? Is there a tutorial on Building and app Bundle somewhere? All I have been doing is Changing the output from my working .APKs to .AAB. Which shows the error I posted above.

I assume it is me, because if I simply make a Blank .aab application. It builds fine!

Thanks in advance...

Display More

Hey Ricky. I had the same issue. I solved it by selecting BUILD API 29 (the latest version)
Hope this helps!

Quote from iamjot

Hey Ricky. I had the same issue. I solved it by selecting BUILD API 29 (the latest version)
Hope this helps!

I'm running on MMF2.5 DEV 292.12 on Android Api 29 Target version 9.

Thanks for the info, but it unfortunately isn't that.

Are you using by any chances the OBB extension object with app bundle?

Quote from Fernando

Are you using by any chances the OBB extension object with app bundle?

These are what I am using.
Please login to see this attachment.

Maybe better take a screenshot of the Extensions tab in the Data Elements editor, easier than figuring out what objects correspond to those icons

Latest issue I just found, besides MMF2.5 DEV bugging out a ton more now then ever before.

I tried to compile an .APK with an older Api and Target version and I get error messages about this api is not compatible with Gradle.

What is that about?

As far as bugging out goes.
ANDROID / WINDOWS
Sometimes MMF2.5 DEV becomes unresponsive after running an app.
Sometimes dragging to move a code no longer works after running an app.
Sometimes the copy feature stops working when trying to copy code after running an app.

WINDOWS
Sometimes extensions continue to effect the PC, even after the application has been closed.
( CONTROL X ) is one of the objects that refuses to release its hold on the PC within MMF2.5 DEV. Which even if you put in END OF APPLICATION = Restore all Keys. You get the same result. MMF2.5 DEV stays effected and can only be fixed by ending MMF2.5 DEV and Restarting it.

I know this new MMF2.5 DEV is 292.12 BETA, but common guys. It should be getting better and not worse.

Thanks for all the Hard work though. It is appreciated!

>> I tried to compile an .APK with an older Api

What API? AFAIK you now have to use at least API 26 or 27 . The latest versions of the Android SDK require those APIs, older API build tools are not supported by Google for building apps.

>> Sometimes MMF2.5 DEV becomes unresponsive after running an app.
>> Sometimes dragging to move a code no longer works after running an app.
>> Sometimes the copy feature stops working when trying to copy code after running an app.

Never noticed those issues.

>> Sometimes extensions continue to effect the PC, even after the application has been closed.
>> ( CONTROL X ) is one of the objects that refuses to release its hold on the PC within MMF2.5 DEV.

Could you post a MFA that shows those issues please?

>> It should be getting better and not worse.

There are no changes in Fusion that could explain this, perhaps the issues you mention are either in the previous versions too or happens only on your machine due to some software update.

PS: the official version is now 292.14 and it's not a beta anymore.

I will try 292.14 and see if this cures the problems.
I simply dropped Control x and Created a different code.

Thanks.

Quote

This APK results in unused code and resources being sent to users. Your app could be smaller if you used the Android App Bundle. By not optimizing your app for device configurations, your app is larger to download and install on users' devices than it needs to be. Larger apps see lower install success rates and take up storage on users' devices.

Resolution:

Use the Android App Bundle to automatically optimize for device configurations, or manage it yourself with multiple APKs.

Can you make clear instructions people who have paid for the full version? This discussion is misleading how to act when google play warning appears. My apk game file takes about 10 megabytes. Is google serious that this file could take up less space optimized? What steps should I do when I'm exported apk? So far everything has been a waste of time.

Use Release version 292.14

when you are reading to publish your game application , set all Release Info

Please login to see this attachment.

Then go to Build Type and select Application Bundle

Please login to see this attachment.

And build using Build Menu as done in below image

Please login to see this attachment.

The result is an bundle package for play store, notice that is already signed, then upload your app bundle

for this follow this help

[FONT=Verdana,Arial,Tahoma,Calibri,Geneva,sans-serif]Please login to see this link.

Notice Google help may change at anytime
[/FONT]

292.14 Non Developer Full: I cant see any other build options than Android/Ouya .APK (so anybody else suffering this?)
292.14 Developer Steam: I can see app bundle option, but Google Play Bundle error disappears still cant start releasing. Button is greyed.

Quote from akakaone

292.14 Non Developer Full: I cant see any other build options than Android/Ouya .APK (so anybody else suffering this?)

For the moment this option is only in the Developer version.

Hello
i have a question with .aab files
i only need to upload in "googleplay console" the bundle .aab file?
Or i need also to upload an apk?
It's not very clear for me
thanks
Pit

Quote from Fernando

The result is an bundle package for play store, notice that is already signed, then upload your app bundle

for this follow this help

[FONT=Verdana,Arial,Tahoma,Calibri,Geneva,sans-serif]Please login to see this link.

Notice Google help may change at anytime
[/FONT]

If you build a bundle, you don't need the APK file. When you use a bundle, Google will build the APK file from the bundle file before sending it to the user (this allows them to include only the libraries that are used on the user's device, this reduce a bit the size of the APK downloaded by the user).

Merci Yves !

Bonjour j ai remarque au moment de la verification du APK sur googleplay console qui m’affiche que le mode d'affichage et sur Opengl es 1.0 mais dans fusion mon paramétré sont sur OpenGL 3.0 les erreur et de leur cote ou fusion au moment de faire la compilation change le mode d 'affichage ?

Hello I noticed at the time of the verification of the APK on googleplay console which shows me that the mode of display and on Opengl es 1.0 but in merger my parameter are on OpenGL 3.0 the error and their rating or merger at the time of doing does the compilation change the display mode?