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

Latest error:

starting a Gradle Daemon, 1 incompatible and 1 stopped Daemons 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 21s
27 actionable tasks: 27 executed

Fernando, I want to participate in the beta test (292.11)

Just a side note.

No issues at all with uploading a .APK to AMAZON so far.
I will let you know, if everything worked as it should. I.E. They release it.

If anyone is publishing on this beta - I've picked up some display issues which I did report concerning the navigation / status etc. bars covering parts of the display.

Work around if you're going full screen (display status bar not ticked):

• Switch on immersive mode
• Set your minimum target to about Android 4.4

I have tried every possible setting and every combination of settings but I can't get the game to display correctly on an Android 4.2 device and simultaneously on higher Android devices with this beta.

From 4.4 onwards my devices work fine. I don't have a 4.3 test device so I have no idea if it will work on that.

If you're not using full screen (display status bar ticked) - then you should be okay.

Quote

Work around if you're going full screen (display status bar

not

ticked):

[LIST=|INDENT=1]
[*]Switch on immersive mode
[*]Set your minimum target to about Android 4.4
[/LIST]

Display More

did you try with api 26 and see how it behave with 4.2

Quote from Fernando

did you try with api 26 and see how it behave with 4.2

No, I wouldn't be able to publish the game anywhere with api 26 and I no longer have it installed.

Was there some specific reason you'd like me to try that? Because I can reinstall it?

But the navigation bar popping up over my game, on that tablet - has been happing since I started using Fusion Android - and I always solved it before by ticking the display status bar button at start-up and then using the Android and Android+ commands to go full screen on a cell phone - with your latest beta I can no longer do that.

the idea is to see fi behave different not to be published

Sweet. AMAZON, has no issues publishing an .APK with the latest MMF2.5 292.11 api29 target 9 build. (AUG.27/2019)

Please login to see this link.

Quote from Fernando

the idea is to see fi behave different not to be published

My results with api 26 and target Android 8.0 were exactly the same as they were with Api 29 and target Android 9.0. Would you like the screenshots?

no need ty for testing

I also have the 64 Bit Problem. Is there a way to get the Android Beta with 64 Bit export? Thank you!

Built apk with 292.11 and still receive this error on Google Play

Error
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: 5.

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

[MENTION=6268]Fernando[/MENTION]

I went back to 292.11 beta as published (without your Android.zip module of a few days ago) - and I could get every setting right on all my devices by changing the order / sequence in which things were done - technically I was starting with everything off, switching everything on using Android / Android+ objects and then switching things on / off again in a particular sequence. If the order wasn't exactly right, then things didn't work out. If the order was right, I got exactly the result I needed. [Switch Action bar on / off, switch navigation bar on / off, switch immersive mode on / off]

With your Android.zip you sent me I can't achieve a successful display on all my devices - regardless of the sequence in which I switch things on / off.

Will you be changing anything related to the display on that module or is it going to stay as per the zip file you sent me a few days ago?

Just checking in with this. As I can not submit new apps either, but I'm in the USA. Same error.

Install the beta of the build 292.12, it should fix the problem.

I can confirm that Google Play is accepting new apps built on 292.12 - the only warning I got was optimisation (i.e. I chose not to use an app bundle.)

Thanks for the additional display settings - I can now get it to display as I need it on all my devices.

Quote from Yves

Install the beta of the build 292.12, it should fix the problem.

Yes 292.12 built apk accepted by Google with no 64 bit warning error! Many, many thanks

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?

I found this but no Products Owners lounge. Please login to see this link.

Quote from Rickyvb

I found this but no Products Owners lounge. Please login to see this link.

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