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 ...
Related
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 think this is a bug in android, android studio or google.
I am able to login to google through the signed apk. But If I upload the same apk on play store it says me Status{statusCode=DEVELOPER_ERROR, resolution=null}.
I want to know how can it be possible that I am not able to login from the app downloaded from the Play Store and I am able to login when I use the same apk from my PC which I have uploaded to play store.
This should not be DEVELOPER_ERROR this should be ANDROID_ERROR, GOOGLE_ERROR or HOW_TO_IRRITATE_DEVELOPER_BY_ANDROID.
Any suggestions on how to resolve this ANDROID_ERROR which they say DEVELOPER_ERROR.
I got this issue few days ago and i solved this by following the google guideliness
1.make sure the google JSON file your adding in App folder must be from the developer account.
2.Update all keys in the firebase account, release and debug key.
3.(important step): there is tab called "App signing" in Release management section in your google play console.
Google has released a new signing service in playstore publish console in which google will signin your app with his keystore. After signing , it will give you a new SHA1 key which you have to add in your firebase account.
after adding that SHA1 key to your Firebase account. try login, it works fine
I was using an existing project to create google sign in. I logged the issue on android as well, but didn't get response till now Issue Repoted Here.
So, I created a new Project with new packagename in Android Studio and copied paste all my required files (Resources and Java files only) from previous project. Created a new project for google sign in and followed the procedure by google
Now I was able to sign in properly.
I think (Not Sure) Android Saved some data from previous project in and it was not cleaned even after cleaning and rebuilding the project. So at last I had to create a new project.
I faced the same problem ... i searched a lot tell i found the solution here.
"Google has released a new signing service in playstore publish console in which google will signin your app with his keystore. After signing , it will give you a new SHA1 key which you have to add in your firebase account.
after adding that SHA1 key to your Firebase account. try login, it works fine"
Thanks to https://stackoverflow.com/users/4943560/sanjay-km
The Google and Facebook logins are working fine in Android Studio Tools, but they're not working on test version or beta testing, so please give me any clue to solve this problem.
I had fixed this issue after contacting google support.
Below is the fix for this issue. Please follow the steps.
To fix google login - Whenever you will create a debug or release apk, please make sure to update Package name and SHA1 fingerprint in your API key at "https://console.cloud.google.com/apis/credentials?project=???".
Please note SHA1 fingerprint will differ for debug and release build, so place it accordingly in google console.
To fix facebook login - Whenever you will create a debug or release apk, please go to https://developers.facebook.com/ and choose your app and go to Settings --> Basic and add your Key Hashes for debug and release.
Hopefully this will fix your issue but if its not then please go to step 3.
Now you have to check for your app enrolled in Google Play App Signing or not. To check this please go to Google Play Console and choose your app that is published in beta and navigate to Release Management --> App Signing. There you will find the text at top "Google Play App Signing is enabled for this app". If so then copy the SHA1 certificate fingerprint from "App signing certificate" and add this SHA1 key as mentioned in 1st step. Now test after 5 or 10 minutes, your Google login will start work in the beta app.
Now you have to add the Key Hash of SHA1 (which we got from step 3) to Facebook console as like mentioned in step 2. Don't worry how to change this SHA1 to that Key Hash format. You can easily get it, please connect your beta version app in Android Studio and try to login in Facebook from your app and check Logcat from Android Studio, there you will find that Key Hash for this SHA1. To add it please follow step 2. Now your Facebook login also will start to work.
Useful link which is related to above fix - https://support.google.com/googleplay/android-developer/answer/7384423
You must generate a keyhash for live sever and update to Facebook. You would have only used development keyhash.
I had same problem. when I debug my code on vscode it was working fine but in internal testing stage sign in with google was not working. I changed my sha-1 fingerprints in firebase with sha-1 that is given by google play console. Here is link; https://play.google.com/console/u/0/developers/8739345695749690484/app/4974329906490558980/keymanagement
if you can't open the link you should follow that;
https://play.google.com/apps/publish --> Select app --> Setup(in release part) --> app integrity
In App signing key certificate part with SHA-1 certificate fingerprint
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.
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.