Use a valid app signing key to continue

[Anke]

Completely unnecessary, complicated, time-consuming, ...

It only takes a few seconds to successfully upload a new app (as AAB) to the Play Store. As I have already explained several times in various posts and guides, you only need a new keystore (if the old one has already been used for other Play Store apps).

1. Export and backup the current keystore.
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.

That's all.
(I checked it again and it took less than 1 min to build a test AAB and upload it successfully to the Play Store.)

---

See also here:

AAB file signing tutorial

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

App Signing publishing error for abb file

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