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.
Related
Android Studio 3.0.1: This is a common problem but I cannot find a solution to my version of it anywhere.
I have successfully created a Debug.apk using Google Maps which runs perfectly on my attached Samsung device.
Next I put the Release Key in the manifest and create the Release.apk which is then uploaded to Google Play
Store. On downloading it then fails to show the map, just the Google Icon and other files.
On Android Studio there is no debug/res/values or release/res/values under app/src and no google_maps_api.xml file
anywhere.
How can I fix this please?
You need to register your API hash with the Google APi console: https://console.developers.google.com/apis
Google signed app
If you are using Google Play signing the instructions for getting all the information you need are here: https://support.google.com/googleplay/android-developer/answer/7384423?hl=en-GB in Step 4:
"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."
Self signed app
You will need to get the SHA1 from the signed key yourself. For a command line to do this see: https://developers.google.com/maps/documentation/android-api/signup
For instructions on adding this to the API console see here:
https://developers.google.com/maps/documentation/android-api/signup
If these instructions aren't clear, here's a more step by step version:
go to https://console.developers.google.com/apis/credentials
choose your project
You should be on a screen that has a list of API keys
Click on the API key your are using in your App
Make sure the "Key restriction" is "Android apps"
There is now a section saying "Restrict usage to your Android apps (Optional). Add your package name and SHA-1 signing-certificate fingerprint to restrict usage to your Android apps. Get the package name from your AndroidManifest.xml file. Then use the following command to get the fingerprint:"
Add the package name and SHA1 for your release app
If you are creating debug apk then you have to add your sha1 key to google api console and also you have to enable google map service in google api console
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."
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.
I have a problem with Google Maps api v2 on my android app.
I have generated the key for the debug certificate and everything works fine, but I can't make it work with the release certificate.
I've generated the key and the alias with eclipse, then I took the SHA1 which eclipse shows at the end of the "Export signed application" process.
Then I generated the api key for android apps in my google api console using
SHA1;package name
But it doesn't work... it works only with the debug key generated in the same way, only using the sha1 of the debug certificate!
Please help me, otherwise I can't release my app
Check your manifest file, I guess you've forgotten to set your release map api key there while exporting with your release key?
Me too faced the same problem during releasing my app to google Play, when I used Google Maps V2 in my app. After succeeding the issue, I wrote a blog post regarding this you can have a look.
As everyone requested, I would say the answer in following steps
1) Sign up your app using eclipse adt
2) Note down the SHA1 finger print which will be displayed at console of your eclipse adt
3) Again go to google console and get API_KEY for your app by using above got SHA1 fingerprint
4) Replace the old API_KEY with the new API_KEY on to manifest.xml of your app
5) Again sign up your app. Your app is ready to be published. But keep in mind that once you published your app to google market, you should be able to release updates to your app by signing .apk using the keystore which you used earlier for release.
Hope this helps ...
There are two files google maps api.xml, one is the debug and release the other, then you should replace the key generated on google website console and enter this file, another outlet is inserted directly into the manifest.
I have Implemented Google maps V2 Successfully.I have made debug as described by Google Map Tutorial. Now its time to release my app with Google Maps on Google Play.For it i have to make release certificate of Google maps.And i am not understanding first step of release certificate fingerprint .
From Where to download Keystore file? it is From api console google
Where is release certificate keystore file?
It's the keystore you create yourself for signing your applications. You don't download it from anywhere. You should not give it to anyone, not even Google.
See http://developer.android.com/tools/publishing/app-signing.html#releasemode for more information.
Me too faced the same problem during releasing my app to google Play, when I used Google Maps V2 in my app. After succeeding the issue, I wrote a blog post regarding this you can have a look.
As everyone requested, I would say the answer in following steps
1) Sign up your app using eclipse adt
2) Note down the SHA1 finger print which will be displayed at console of your eclipse adt
3) Again go to google console and get API_KEY for your app by using above got SHA1 fingerprint
4) Replace the old API_KEY with the new API_KEY on to manifest.xml of your app
5) Again sign up your app. Your app is ready to be published. But keep in mind that once you published your app to google market, you should be able to release updates to your app by signing .apk using the keystore which you used earlier for release.
Hope this helps ...