After uploading a new AAB in the Alpha release track, play console rejects the AAB with “The Android App Bundle was not signed”.
I used “Export and upload a key from a Java keystore” when i setup App Signing in the Google Play Console, because I had the keystore/key from before. In Unity I set up the build for Android App Bundle. Also I set up the Android publishing with the keystore / project key and required passwords. The keystore and key are the same as when I setup the Google Play Console for Google App Signing.
Note this is an updated AAB, the previous version that I uploaded worked fine.
This issue was fixed a while ago. Please use a newer Unity version. After updating to a newer Unity version, if you have a custom gradle build file, make sure to regenerate it based on the template in the used Unity version.
I am having this issue in Unity 2019.4.2f, not using custom gradle files, and only when building Google Play Bundle in Development Mode and attempting to release it as a Closed Alpha Track on the Google Play Console.
This appears to be related to Google Play Console’s security issues with Development/Debugging mode enabled when releasing to an alpha track.
Instead, use the Internal App Sharing for pre-alpha builds that require Debugging mode:
The issue I was talking about should not be present in Unity 2020.1.8f1. Also a Cloud Build should not affect it. Have you tried to recreate the gradle build files with this Unity version?
The recommended way to recreate the gradle build files is to move overwritten files from Android/Plugins to some backup location. Then return to Unity editor. This should recreate the template files which were previously overwritten, but they should be using correct configurations for that specific Unity version. If the files are not recreated automatically, go to the Publishing Settings section in Player Settings and enable checkboxes for the custom gradle templates which you have previously overwritten. After that do the same modifications in newly generated files as you have done before in the backed up files.
If you don’t want to follow the recommended way, you could try comparing the signing sections of the gradle template available with your Unity version and the one you have in Android/Plugins. Look at “buildTypes { debug {” section for “SIGNCONFIG” which should be replaced by Unity editor when building the app.
Is this only happening with the Cloud Build, or do local builds reproduce the issue as well?
Do you have custom gradle templates created with older Unity versions? Maybe the configuration there is incorrect. You could try to recreate them based on the template in the currently used Unity version.
I’ve just hit this issue with 2020.3.20f1 as described here…
I’ve a ‘beta’ UCB config that uses the production keystore and has the development build flag enabled. This has been used successfully in the past (with various versions of Unity 2020.3). I’ve just updated from 2020.3.18f1 to 2020.3.20f1 and have hit this issue.
So a regression maybe?
Even if unticking the dev build flag will produce signed builds, this is no good as certain debug tools are enabled by the flag (so the build would be useless for internal testing purposes)
Our QA investigated this issue and found out that the same problem is reproducible when creating an app in Android Studio. It seems that Play Store does not allow to upload debug builds anymore.
Even for internal builds? That literally makes no sense.
I’ll drop Google an e-mail and see if there is a way around it. All my debug code\tools are triggered by the development flag (as I’m sure is the case with most) so Google are basically pushing you to sideload rather than use the internal test track for its primary purpose.
Did you get any update on this? I’m likewise having the same issue, internal app sharing or not. The crazy part is it actually works if I upload the .aab manually, it’s when uploading from the command line via a script that it doesn’t
Unity 2019.4.28f1, development .aab build via Github actions
Apologies I’ve been on others things for a while, but will be finally uploading beta builds to the stores in the coming few weeks. I’ll re-visit then and report back either way.