I’m working on an android app which was release on Google Play Console in 2024 January.
I used the Windows keystore “mafirstkeystoreformyapp.keystore”.

Because I wanted to upgrade my laptop, I bought a new one, get back my project from my GitHub repository, do my test : everything was ok.

So I formated my first laptop.

But I realised, when I wanted to create a new version for Google Play Console that my app signature/footprint is not recognized :

Your android App Bundle was signed with the bad key. be sure your app bundle is signed with the good key and retry. The imported app bundle should be signed with the certificate associated to the “footprint”
SHA1: XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:B2
, but the certificate used is associated to the footprint
SHA1: XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:A5

So I contacted the Google Play Console support that made me :

• create a JKS file from my MAUI project :

  keytool -genkeypair -alias upload -keyalg RSA -keysize 2048 -validity 9125 -keystore keystore.jks

• Export the certificate for that key to PEM format

  keytool -export -rfc -alias upload -file upload_certificate.pem -keystore keystore.jks

• Update the certificate from my account (2 days needed)

But this .jks file has no meaning for me : windows keystore are recognized as .keystore file, so it is useless

Is there a way to transform this .jks to .keystore ?
Or to easily recreate a valid Keystore from an existing “Importation Key Certificate” ?

There is many stackoverflow about the second question (which is linked to the first one) but, even if the response seems to be no, it look like the current situation evolved.
Android: I lost my android key store, what should I do?
I lost my .keystore file?
Recreate keystore file from private key and certificate

What I already tried

I found this : Android Package Signing for .NET MAUI app
It’s pretty close but the user issue is linked to his “App Signing key, whereas I must to use the App Importation Key (so his resolving steps cannot be done)

I tried to :

1. create a new .keystore from Visual Studio, get the .der key from Play Console to add it : KO (the certificate is added but not used during Distribution)

2. create a new key store, delete the default key, import the .der key from Play Console to add it : KO (the keystore seems to be “corrupted” and so Visual Studio doesn’t allow me to Distribute the app)

3. import the .der key from Play Console and create keystore from it : KO (the keystore seems to be “corrupted” and so Visual Studio doesn’t allow me to Distribute the app)

4. (do 3 before that) import the new keystore from the dedicated windows dialog : KO (a java error appears)

       à System.Runtime.InteropServices.Marshal.SecureStringToGlobalAllocUnicode(SecureString s) 
    à Xamarin.VisualStudio.SecureStringExtensions.ToUnsecureString(SecureString input) dans D:a_work1ssrcCoreVisualStudioExtensionsSecureStringExtensions.cs:ligne 16
   à Xamarin.VisualStudio.Publishing.Presentation.ViewModels.AndroidImportKeyViewModel.<ImportAsync>d__49.MoveNext() dans D:a_work1ssrcCoreVisualStudio.PublishingPresentationViewModelsAndroidImportKeyViewModel.cs:ligne 138
   

I used Keytool to update/create keystore :

keytool -import -alias vilolaboratory -file upload_cert.der -keystore vilolboratory.keystore