I am unable to export or encrypt the android.keystore file for the Google App Signing. My App was updated back in 2018 lastly. How do I solve this?

[Anke]

@MIT-Inventor

Yes, but i am trying to sign while using a newly exported keystore. Should i not?

No.

@MIT-Inventor

Then you tried to publish this app (APK) on Play Store? Yes, for the new apk. fingerprint is not the same playstore says

Then the keystore is not the same as with your app (APK) from 2018.

---

See also here:

How to release / update an App on the Play Store → Requirements

In order to be able to release an app / update in the Play Store, at least the following requirements must be met: The version code is higher than the current version. The packageName is the same (as the previous / original one). The keystore is identical (with the previous / initial version). The targetSdkVersion corresponds to the minimum SDK required by Google (4a) from Aug 2021: SDK 30 for new apps and from Nov 2021 also for updates) (4b) from Aug 2022: SDK 31 for new apps and from Nov 2…

How to upload and publish an app in the Play Store → AAB or APK

If you want to upload and publish an app in the Play Store, the following should be observed: Apps that were published in the Play Store before Aug 1, 2021 can still be uploaded as APKs in the Play Developer Console (even after Nov 2021) and therefore do not need to switch to Google App Signing (which simplifies it). Apps that were published in the Play Store after July 31, 2021 must use AABs and also Google App Signing. To test such apps in advance, you should always have an APK generated…