Android Cloud Build not signing AAB even with valid credentials

Unity Services
1

Hello!

I’ve a well established\used set of config’s for a particular game. But today I created a new build (for internal testing) and it’s failing the upload to Google Play with…

The Android App Bundle was not signed.

I’ve checked the config and it reports no errors and is pointing to a valid (upload) keystore. I’ve also checked the full build log (for sign, credential, keystore etc) and all it finds is this…

Assigned value ‘True’ to property ‘useCustomKeystore’ in ‘UnityEditor.PlayerSettings+Android’

Please could someone advise if this could be a UCB issue and if so, what I should be looking for in the log?

The config targets Unity 2020.3.20f1

The Android App Bundle was not signed
2

Update…

Looking at an iOS build log, I can see the following…

43: installing iOS credentials for
44: Signing credentials:

Which is not present in the Android build log.

So unless the Android builds use a different naming convention, I’d say this is definitely a UCB.Android build issue.

3

Hello!

Please could someone from Unity comment on this?

I built a new version (for internal testing) this morning and it failed the upload to Google Play again.

Same error as above… The Android App Bundle was not signed

4

Anyone please?

This is clearly a UCB issue…

5

Hey @PeachyPixels – apologies for the delay circling back to you on this. Have you submitted a support ticket? That’s usually the fastest way to get issues like this looked at and to hopefully get a solution to you ASAP.

6

Hi @rajivrao , I did yes. @JuliusM replied in the other thread (above) and it turns out Google has put a stop to uploading development builds to internal tracks. I’m going to contact Google about it (for what good it’ll do) as it just seems an odd decision to me.

Thanks anwyay!

1 Like