I have published an app on Google Play but map is blank and I cannot figure out how to find the resulting api key that I need and where to put it. I have my SHA1 fingerprint and my api key that is for debugging.
Works great on my device but not after publishing. Every video and post I see on this is from years ago and doesn't seem to work. I can't figure out what I'm doing wrong.
Go to your Google play console where select the app and in left side : Release management=> App Signing=> copy SHA-1 certificate inside App signing certificatemodule and paste into the Google cloud console and add this SHA1 with your project and save it . it will work . it works me.
Related
This question already has answers here:
Published App on Play Store can't communicate with Google Maps API and Facebook API
(6 answers)
Closed 5 years ago.
As mentioned in the title, the Maps Activity shows blank (with Google logo underneath) after I've uploaded the application. I am aware this question has been asked many times but none of the solution is able to resolve my issue.
This is what I've done so far:
Generated Google Maps Release API Key (with SHA-1 signature) following the official guide here and placed it under the release/res/values/google_maps_api.xml
Place the Release API Key hardcoded into the AndroidManifest.xml
Clean and rebuild the project
This is the result:
The Maps Activity just worked perfectly fine if the app-release.apk is installed manually to the device before upload to the Play Store.
The Maps Activity shows blank if the app-release.apk after the app-release.apk is uploaded to the Play Store.
Solution:
This answer solved the issue I am facing. The reason the Maps activity shows blank previously because Google Play re-signs the app with the original app signing key I've provided. So just copy the Google SHA-1 and paste it to the console where the Google Map API Key is generated.
If GMap activity is added in any project then there are two google_maps_api.xml. One is for Debug and One is for Release.
Probably you've entered the key in Debug only as when we add Gmap activity, only google_maps_api.xml opens. So put your key in Release also. How?...see.
Click on TODO on the Bottom bar of Android Studio.
Click on scope Based tab of TODO.
Now there are two google_maps_api.XML, open each and copy your key
to XML with no key (YOUR_KEY_HERE).
This also happened with me.
You have missed adding the permission, try checking by including the permission.
<uses-permission android:name="android.permission.INTERNET" />
I have seen several threads around this issue but I am still struggling.
My app is failing to sign in on Android with:
Unexpected response code 403 for https://www.googleapis.com/games/v1/players/me?language=en_US
I had this all working about 4 months ago but my hard drive failed and I am trying to get things working again on a newer version of Unity. I am only having this problem with NEW builds. My old apk still works fine so everything must be fine in the Google Play Developer Console. Something is not setup right in Unity.
I have tried with and without setting the "OAuth2 Client ID" from the Developer Console in the Android settings.
I have tried setting the keystore to .android/debug.keystore using the androiddebugkey with "android" as the password for both.
What else could it be?
So to sum up my comments up in an answer, that might be useful to somebody else.
1.) An app authenticates itself towards the Google Play Services with the combination of Keystore and Package name.
You can't sign in without or with another keystore. So you should always backup the keystore file together with your project in a version control system, that is safe from a single hard drive failure.
2.) If you lose keystore file, you can not update your app anymore.
But you could create a new app and link it to the same Google Play Game.
I am doing some modification in an existing apk that i got from my client to modify. I have decompiled application using apktool, changed some resources (like some strings from strings.xml) and recompiled/built it again using same tool. Then I signed using one_click_signer tool that I found somewhere of the google.
But when I install it on my device then google maps does not work anymore as it was working with original apk on the same device.
I have searched a lot about this but did not got any solution.
I reviewed this link and many more and come to conclusion that I need to sign the apk with same key that was in original apk.
So can anyone please tell me:
how can I sign the apk again with the same key and make map work?
or is there any other way to make maps work properly?
Solution That I found and worked for me:
Thanx for
#apmartin1991's answer . .
I created a google api console project and got got the generated key.
then I replaced that key in android-manifest.xml file and resigned the application.
It worked.
You will need to contact your client to get the .keystore file so you can sign it with the same key OR you can sign it with your own key and allow your key to be used with google maps, You can do this from the Google API console.
However if your clients app is on the appstore and you want to update that you MUST use the same key or it will be impossible to update it.
You need .keystore file to use the same key. If you dont have .keystore file you need to generate a new one and register a new key in google maps console.
You have all the official instructions here.
I received a release.keystore from the developer that was working previously on the project.
I created a custom debug.keystore based on release.keystore to test the app.
Some of the functionality of the app is broken comparing to the app on the Google Play which makes me think I might not have a valid key. For example Maps don't display correctly (gray square).
Is there a way to find out if I have a right key, that the previous app was uploaded with?
thank you!
don't create a debug key from it. Just sign the app with the regular key and then test it.
I believe that the maps API is tied to your release key so it will not work in your app unless you sign with your release key
I build and sign my android app. Now I publish on google play but when I install on google play, google maps doesn't work. I read some article about this issue but I dont fix it.
What can I do after signing ?
I don't know if it is still an issue. But you needed different API Keys for different keystores.
I had the same problem, but with Facebook. You have to sign your application with your keystore publish key, because your preveous key is a debug key and it doesn't work after publishing app.