Do I Need Android Studio For Upload Key Unity3d

Question

I'm trying to publish a update of my awarding on google playstore.

because I activate the Google Play App Signing service for this app, I have to sign it with an upload certificate provided past the shop in order to publish information technology.

https://support.google.com/googleplay/android-developer/answer/7384423

I tried many ways to do that in unity without success

everyone knows how to do that?

Answer 1

Create keystore file "keystorefile" with unity. And then import "upload_cert.der" downloaded from google play console to keystore.

                                                  keytool.exe -importcert -file upload_cert.der -keystore <keystorefile>

Answer 2

Hullo. I just had this problem myself and being really new to all this had to take some time work out the trouble in more than detail. winxalex answered the question, but if you demand a step by step:

You lot need to download your certificate from your google play panel.
You need to import your certification into the keystore you used the beginning time you exported from Unty. You probably saved that somewhere important.
Yous need to use a plan chosen keytool.exe. The path to that program probably looks something like: C:\Program Files\Coffee\jdk1.8.0_192\bin
If you become at that place in windows explorer and type "cmd" into the address bar, information technology'll open that location in the concluding.
Y'all then need to use winxalex' lawmaking above in the terminal (after having navigated to the location of keystore.exe, as yous did in step 3
You need to point that code to your document and to the keystore you lot're importing the ceritificate into. your last teaching volition look something like the following:
keytool.exe -importcert -file "C:\Users\MyAccountName\DesktopOrWherever\deployment_cert.der" -keystore C:\Users\MyAccountName\DesktopOrWherever\user.keystore
keystore.exe will ask y'all for the password you used and whether you trust the app, and so update the keystore
Make sure Unity is using that keystore when you export your app

Those are the steps that worked for me. I promise this helps others.

Answer 3

Hey! From what you've described, information technology sounds like you followed the steps for a New App in the support page y'all linked. If so, you have to apply the keystore and alias you used to signed your apk the first time, for all updates.

Background: If you opt in to let google handle the app signing for yous, you but need to sign with the 1 fundamental (the upload primal) and google volition manage your app-signing key.

If you didn't brand a keystore, you may take uploaded an unsigned app (which I don't think you tin publish).

If you're managing your own keys nevertheless, the steps are different, and I tin help with that also - but let me know.

Answer 4

I call back there'due south quite a chip of misunderstanding around this. This is how I eventually got information technology to work:

You don't sign your app with the certificate downloaded from Google. You likewise don't import it into the keystore created past Unity. If you do and then, Unity won't see it because what yous imported is only the public key, and you need the private key to sign the app. The private cardinal is held by Google - you don't have it.

Then what y'all do is you create the keystore and cardinal in Unity and sign your app with it - merely like earlier.

In Google Play Console -> App releases, you can meet this: "Permit Google manage and protect your app signing key (recommended) Enabled.

Upload key: The key you lot use to sign your showtime release. Sign every subsequent release with the same central to verify it'due south from you. Continue your upload cardinal safe. If it'south ever lost or compromised, contact developer back up to supersede it."

On the App Signing folio there's this: "How information technology works

You digitally sign each release using your upload primal before publishing it to a runway in the Play Console.
Google Play uses the upload certificate to verify your identity then re-signs your release using the app signing fundamental for distribution.
Each Android device checks the release's app signing certificate matches the certificate of the installed app earlier updating information technology."

So what Google does is once you upload your app, they sign the app one time over again - this fourth dimension with their private fundamental. And the public fundamental for that signature is what yous downloaded from Google Play.

Users will at present see that your app is signed not with your Unity upload primal, but will Google's. So if you want to register your app's MD5 signature somewhere (like API providers), yous need to utilise the certificate downloaded from Google - that'south the only reason you need it - you don't sign with it.

Some more info about this: https://stackoverflow.com/a/52923860/931409

The thought is that your upload key is only used to let Google know it's y'all, and not distribute the app. And if you lose information technology you can ask Google to change it. Simply if that fundamental was used to really distribute the app and you lose it - information technology'south game over. That'south why the distribution is done using Google'due south cardinal which hopefully is kept much safer :)

Answer 5

If, like me, you came hither because you are having issues with long iteration fourth dimension while testing Google Play Games Services code ....

My issue involved:

Google Play Panel controls my app signing key
Unity'southward keystore is applied to my Unity builds
Therefore I tin't exam Google Play Games Services code without fully uploading and publishing my builds through the Google Play Console

This thread is how I finally got that stock-still.

https://github.com/playgameservices/play-games-plugin-for-unity/bug/2981