Status Update
No update yet.
Comments
sg...@google.com
Thank you for the report.
Some questions:
- Is there any more information on the issue that Play found?
- Is it from Play installing the app and trying to click around looking for crashes?
- Is there a stacktrace provided by Play so you can see where in the app this is happening?
- Is the class
com.medlinx.helzy.Appyour main class? - You mention testing the universal APK is that also the APK that Play is finding issues with, or are there perhaps multiple APK generated from your AAB and it could be one of the others?
- Are you using dynamic feature splits?
There has been some R8 updates to the 8.6 version not part of AGP 8.6.1. You can look at
ak...@gmail.com
Is there any more information on the issue that Play found?
Is there a stacktrace provided by Play so you can see where in the app this is happening?
Unfortunately, I can't find more info from the Play.
Is it from Play installing the app and trying to click around looking for crashes?
I guess, someone (robot or person, not sure) launches the app to review it, and the app is not loading.
Is the class com.medlinx.helzy.App your main class?
Yes, it is the main Application class, which is specified in manifest. It resides in the main :app module.
You mention testing the universal APK is that also the APK that Play is finding issues with, or are there perhaps multiple APK generated from your AAB and it could be one of the others?
I get the universal apk from the Play itself, under App Bundle Explorer - Version - Downloads - Assets, and it works fine. And I don't know what exact apk Play is generating during its review process.
Are you using dynamic feature splits?
We are not.
Another thing I noticed, is that the problematic bundle is not installing via shareable link:
Whereas the working release installs just fine:
I apologise for the lack of information, it's all very mysterious and it could very well be a bug on Play side - just hoping to get some pointerss, maybe there have been similar reports.
ak...@gmail.com
Okay, nevermind. I upgraded AGP to 8.7.3 (and gradle to 8.9), and created a release - now review passed without any issues.
Not sure if it was AGP at fault, or there were some pecular problems in Play the day of the previous release. But nevertheless, the issue can be closed now, thanks for help!
sg...@google.com
Thank for reporting back that you resolved the issue.
Description
We are trying to update from AGP 8.2.1 to 8.6.1 for our multi-module app, to raise our target sdk version to 35.
Initially there was a problem with :minifyReleaseWithR8, but it was solved in
isMinifyEnabled = falsefor all modules except the main :app module.The release build was building succesfully, the app was launching and working perfectly. However, when we tried to release the updated version on Google Play, the update was rejected during the review:
This is very strange, because if I download "Signed, universal APK" from App Bundle Explorer in Google Play Console, the app installs and runs without any issues. And the inspection of both the .apk and .aab files shows the presence of App class in path "com.medlinx.helzy" in classes2.dex (the same as aab and apk of previous, working, release).
What could be the issue? It seems something breaks when Google Play generates apk from aab during the review process.
All we did was:
isMinifyEnabled = falsefor release build in common configuration that is used in all modulesFor now we rolled back these changes and were able to pass the review and release the update, but we would still like to update AGP asap.