I'm having a problem. I had a debug md5 code that was generated. I switched the code so I can publish my app, I now get a grey screen when i run my emulator. The map doesn't show up any more. Is this a problem? should i trying getting another md5 code to use? Or can the debug code work?
You must generate another API code. Your Google Maps API code is generated based on the keys your app is signed with, therefore if you sign your app with release keys, you must generate an API code which is generated using the same release key.
Related
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.
My app is a geolocation app which silences mobile on entering a geofence.I am able to see googlemaps completely on my debugging apk .however,after downloading it from the playstore,everything works fine except it doesnt show the googlemaps.Instead it shows
Please let me know the problem with that.does the google maps key needs a fix?
well what you have added is the debug API key which would support your google map in debug mode if your to install your application directly from the Android Studio.
what you need to do is add release API key to the project,
There are two different API keys that you need to deal with while working with Google Maps one is debug and other one is release Key.
you need to generate SHA1 key in release mode and create a API key using this SHA1 and your project package name, so you can see the Google map work in release mode,
easiest way to get SHA1 for release mode is to run your application in release mode and while rendering Google map it would throw you an error along with SHA1 key with which you need to make release API key
I have an application with a Google Maps in the center. However while programming and debugging it all worked fine. Now we created a release application and we found out the current API key is not working.
Now I created a SHA1 key and added my package name to it inside the developer console. It generated a key for me, however this key isn't working either in a release apk.
I tried several things like regenerate it a few times or reinstall the app.
Anyone know what might go wrong?
Make sure you're creating your SHA from the key that you're signing the application with. This SHA will be different than the one that you use for the debug builds.
Make sure that the application is actually getting signed correctly.
Make sure that the package you're providing for the key is correct.
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 am implemented Google map in my application it's showing Google map on device before creating signed apk. When i created signed apk then it's not showing Google map on device so I am not getting what I did wrong so any one can give me suggestion.
Without any additional information to go on, I'm going to assume you created the release APK still using the debug Google Maps API key. You will need to use create a API key for the release APK. See: http://code.google.com/android/add-ons/google-apis/mapkey.html#getfingerprint
If its something else, could you add logcat output to your original post?