I know how to publish an normal application in (Google Play Developer Console). I want to know how to publish a game in (Google Play Developer Console) which is implementing Game Services. My game application is running well and Game Service is working properly.But now I am confused about debug sha1 debug key and sha1 release key.
and do I have to linked my game with both debug and release sha1 keys?
I have provided details for generating and specifying the release version of the SHA1 fingerprint in this post: Getting Android Google Map v2 working in release version by generating SHA1 fingerprint for API key
I think you're referring to release certificate and debug certificate which you need to keep.
You should create two client IDs, one with the release certificate
fingerprint and another with the debug certificate fingerprint. Make
sure to use the same package name for both. This allows Google Play
games services to recognize calls from your linked APKs that are
signed with either certificate. For more information about certificate
signing for Android, see Signing Your
Application.
When all is setup, move to Testing and Publishing Game Changes.
Related
I am enabling one tap login in Android app and I am following https://developers.google.com/identity/one-tap/android/get-started
I have confusion about the SHA-1. When you create a android client, then it says production-or-debug sha-1
I tested with debug sha-1 during development and it worked. I uploaded the app to Play Store and changed the sha-1 which I got from production key store. But it is still giving this error: "Cannot find a matching credential"
I have tried using both debug and production keystore sha-1 but they do not seem to work with the app downloaded from play store.
It is pretty confusing that whether I should be using debug or production keystore sha-1
Here is my understanding
While I am am running debug build during development then I should be using debug keystore sha-1
For apps downloaded from Play Store, I should be using the production keystore sha-1
The #2nd case does not seem to work for me.
What if I need to test during development while the app is is live on Play store? Should I be creating two Android clients? one with debug sha-1 and other with production sha-1
I have Android app which include Google Maps It was working fine before releasing the app, but after releasing the maps are not shown .
Although I've added SHA-1 certificate fingerprint from google console after releasing and added it to the restrected apps
SHA-1 after releasing
API Key Restrictions
So the 2 SHA-1 are included with the package name, the Maps works fine when running the app directly from android studio, but it shows nothing when downloading the app from playstore, any Ideas ?
It's because Google Play is signing app with different SHA-1 Fingerprint, so you need to take it and register in google developer's console
I recently had the same problem. Please make sure you have set your release api key on your app resources.
In your app you might have:
src/debug/res/values/google_maps_api.xml
where you set your debug key and also:
src/release/res/values/google_maps_api.xml
where you must set your release key. If you have created only one API Key with both SHA-1, then you must introduce the same as in debug.
One more thing, in the Google Developers Console besides the debug SHA-1 and the Google Play Console SHA-1 I also add the release SHA-1 of the keystore I've use to sign my app.
I have google login in my app which was working completely fine before publishing my app.But after publishing i am unable to sign in due to change in SHA key. So to change this i'm following steps in Released Management->App Sigining on my play console.
I have downloaded PEPK tool but for step 2 I have command
$ java -jar pepk.jar --keystore=foo.keystore --alias=foo --output=encrypted_private_key_path
I dont know what is foo.keystore, foo and encrypted_private_key_path
can any one please help me on this?.
While working with any of the APIs related to Google Developer Console in Android, you need to configure two different SHA1 keys, i.e. one for debug and one for release. It happens most of the times that, we forget to to generate the SHA1 key for release version. I believe following link will help you to generate SHA1 keys for both the versions.
SHA1 Key for DEBUG & RELEASE ANDROID STUDIO MAC
If you are using Google Play Signing to allow Google Play to sign the release version of your app for you, then you will need to register the SHA1 key from the release version of your app with the authentication console. You can get this key following the instructions here:
https://support.google.com/googleplay/android-developer/answer/7384423?hl=en-GB
"If your app uses any API, you will usually need to register the certificate of the key Google signs your app with for authentication purposes. This is usually done through the fingerprint of the certificate.
To find the certificate of the key Google uses to re-sign your APK for delivery:
Sign in to your Play Console.
Select an app.
On the left menu, click Release management > App signing.
From this page, you can copy the most common fingerprints (MD5, SHA-1 and SHA-256) of your app signing certificate. If the API provider requires a different type of fingerprint, you can also download the original certificate in DER format and run it through the transformation tools that the API provider requires."
Recently, I was working with Android Maps V2. I came across debug.keystore and release.keystore. What is the difference between them? Why do we have to use both?
debug.keystore is merely for developing and testing purposes, so using that you can't release your app to Google Play using that only.
Caution: You should not release your application to the public (via any source) when signed with the debug certificate.
release.keystore is required only when you want to release your app to any app store.
For more information, see Signing Your Applications, subsection Signing in Release Mode.
You can work on developing the Android app with debug.keystore. The release.keystore will be need when your app is ready to be submitted as an app on Play Store.
debug.keystore is used at the time of development, where as release.keystore will be used at product release... link
debug.keystore you call for testing purposes for developers, because it contains the default alias and default key password and also by using this you can not publish your app into the play store.
release.keystore you call for the final app certification keystore. This keystore has its own alias and own key password. And for every new publish of your app, you must generate an signed APK file by using this keystore.
For more information, see Signing Your Applications.
You cannot publish your app to Google Play with debug.keystore, and users won't be able to download your app.
debug.keystore is used to generate Google Map API V2 key for Debug purpose . release.keystore is used to generate map key before uploading app to Google Play.
Previously I have implemented Google maps v1 .It had publishing key and debug separately .But now i have implemented Google maps v2 with the help of this tutorial.In it they haven't mentioned any publishing key .Do we need publishing key to publish app on google play
You need a release key for publishing you app to the Google Play Store.
A tutorial can be found here.
Note that you need the SHA-1 fingerprint of your certificate as stated in the given link:
Release certificate: The Android SDK tools generate this certificate
when you do a "release" build with either ant program or Eclipse. You
can also generate this certificate using the keytool program. This
certificate can be used with an app you release to the world. Once you
have the correct certificate for your needs, you can display its SHA-1
fingerprint using the keytool program.