App Signing publishing error for abb file

[Tonga1]

Trying to publish a new app and getting the error

"You uploaded an APK or Android App Bundle that is signed with a key that is also used to sign APKs that are delivered to users. Because you are enrolled in Play App Signing, you should sign your APK or Android App Bundle with a new key before you upload it."

Is this normal for every new publishing? I found a FAQ "Tutorial for signing an ABB file", which is quite complex and I'm not being successful doing it from a Mac. Does one need to create an app signing key for each new App now?

Thanks in advance.

[Anke]

@Tonga1

"Tutorial for signing an ABB file", which is quite complex and I'm not being successful doing it from a Mac.

Tutorial for signing an AAB file

For new apps (i.e. for AABs) you just have to make sure that a new keystore is used. That's all.

1. Export the current keystore and backup it.
2. Delete the current keystore in the Designer (AI2).
3. Reload the browser (not quite sure if necessary).
4. Build the AAB (a new keystore is generated then).
5. Upload AAB to the Play Store.

[Tonga1]

Thank you @anke. That worked. Since I have other apps published, i assume that i'll need to import the keystore which I backed up before publishing updates? Shouldn't be a problem keeping track of the keystores, again, thank you very much!