I am experiencing a persistent signature mismatch error when trying to upload a new app bundle (.aab) to Google Play Console, and I have been stuck on this for 3 months.

- I requested and received approval for an upload key reset from Google Play support, and the email confirmation stated the new key became active on October 29, 2026.

- The SHA-1 fingerprint currently expected by the Console is: BC:29:5B:59...

- However, every time I sign my .aab file locally using jarsigner and my current keystore, the Console rejects it with a signature mismatch error, showing a different fingerprint.

- I am working on a Linux Mint environment. I verified that my keystore password is correct and that the app bundle is signed using the exact command:

jarsigner -verbose -sigalg SHA256withRSA -digestalg SHA-256 -keystore signing.keystore "Mesa & Dominó.aab" my-key-alias

Despite this, the Play Console still blocks the upload. Is there a hidden caching issue in Google's backend after an upload key reset, or how can I force the console to recognize the new signature?

Attached are the screenshots of the error and the original key reset confirmation email.