Signing an AAB with a wrong keystore - error from Play Developer console

  • Was the app (the AAB update) built with the same builder?
  • Has the keystore been deleted, overwritten or changed in the meantime.
  • If yes, is there a backup of the old (original) keystore (android.keystore) that the app was signed with before/from the beginning?