Zipalign -v -p 4 my-app-unsigned.apk my-app-unsigned-aligned.apk It needs to be signed manually (in step 4) with the *.jks keystore file mentioned above (keystore.jks).įirst zipalign the unsigned archive (make sure to add C:\Program Files\Java\jre1.8.0_191\bin to PATH in User variables): This opens a folder where an unsigned *.apk file resides. In the Archives menu option, select the latest archive and click Open Folder. Go to Visual studio and archive the Android project from Build/Archive When it becomes active follow these steps: Now that I have a *.pem file and *.jks file, how do I create the new APK file for my Xamarin Android project, signed with the new upload key in Visual Studio?Īfter sending the *.pem file to Google Play Developer support in order to reset the Upload Key, they confirmed it was successfully reset (yay Google App Signing) but it takes a couple of days for it to be active. Keytool -export -rfc -alias upload -file upload_certificate.pem -keystore keystore.jks Keytool -genkeypair -alias upload -keyalg RSA -keysize 2048 -validity 9125 -keystore keystore.jksĮxported the certificate for that key to a *.pem file: Generated a new upload key using the command line: In that folder i ran the command lines in the next steps: (dont know if i had to do this to generate new upload key) Generated a new archive and new keystore for the Android project in Xamarin and exported the APK to a folder. Luckily I was registered for Google Play App Signing so they were able to reset the Upload Key for me. When I wanted to upload an update to the Google Play Store with the keystore that I thought was the right keystore, Somehow I managed to save the wrong keystore for my Android app that I developed using Xamarin and already published.
0 Comments
Leave a Reply. |