Signed apk file my application for PlayStore, no maps - android

I have an application on the playstore that uses maps. Although it worked fine in debug, map doesn't appears in realease.
I did the following steps:
- activate maps v2 on google console
- get the API key
- paste the API key in my manifest
- export the apt file with eclipse tool to generate and sign

It's happen because your given SH1 fingerprint signature does not match with your app's SH1 . When you have get API Key from API console you enter the SH1;package_name_of_your_app this SH1 is not the exact SH1 for your APP. For this reason map is not showing.
This is happen for me also. If any thing need please ask me.
Edited Answer
You will get this type of thing

When exporting in Eclipse like that, you will see a SHA1 signature for the release app. Use that one to create a new key, and add it instead. Then continue, as usual. The problem is that you have to have different keys for release and debug. Not sure where exactly was this written, but this should be enough as a source I think.

Related

google map not show in release apk using android studio

I am developing an app, here I'm using google map in debug mode map shows correctly but in release mode map not showing and shows only current location.
By using google map API I have tried but still its not working and also I find the SHA1 by using keystore(i.e. keytool -list -v -keystore file path.jks) then also its not working.
By using following views I tried and found the SHA1 key but map not shown in app.
Release APK file not showing google maps
How do i do?
Have you set your google_maps_key in both debug & release folder in google_maps_api.xml.
If not please, set it. You can find both folders inside Project structure.
See image for reference.
Generate API key access using release key-store. And set Google API console.
Go to google API console.
crate new project
generage API key
enable your service
add API key in your project
OR
You can simply follow this developer guide LINK.
If you have troubling in getting SHA-1 key. You can easily get it by running Signing-report gradle task as below picture (in Android studio).
I solved it by looking at Google Play Console in the left menu select configuration, then integrity of the app and then copy the sha1 of the upload key certificate that is below of the SHA1 Certificate of the app signing key and add it in the same API key of Google Cloud Platform. This way I didn't have to make changes to the apk.
If it doesn't work for you, add both and try.

Google Maps not showing on release apk

Hello when I put the release apk of my google maps app on my phone it works great, but it does not work on other phones which is strange becausd i have the right api key and the right sha1 fingerprint of my keystore file??? Please help. Thanks.
This is because you need to generate a separate key for your app which is going to be released.In this key you need to use the SHA1 of the signed apk.
Please check This link for detailed steps
For signing your app in android studio and obtaining new key,you can use This and This.

android: google map v2 not working when I run from my computer

Google maps v2 is implemented in my app. It works fine when it is run with other computer.
But it is not showing Map when Apk is generated with my computer.
Is there any settings to change in my PC?. Please suggest me.
Google maps API key is generated with Signed key.
You are absolutely right you do not need to change the api key it is unique.
So you don't need to change anything in manifest.xml.
But, As you said when you run the project from your computer it does not showing the map. Because when you run the project by default it sign the apk with debug.keystore.
So now what you have to do is, just generate the SHA-1 from your pc using debug.keystore and make entry of that SHA-1 in google api console.
You can add multiple SHA-1 in your project settings at google api console.
Just see the screenshot you will got the idea.
when you run form your computer then debug.keystore used and when you create apk then keystore is change and also SH1 key is changed so your map is not show when you create apk.
Solution: create new api key for apk, use this key when you create apk. this link help you to get SH1 key from keystore

Google maps v2 android api key working only with debug key

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.

problems with android maps apiv2 after signing apk

I'm having a serious problem
When i build the apk via Eclipse everithing fine and the map is working very well
But when i sign my apk with Eclipse and move the signed apk to my phone the map activity not working, its not collapse it just show gray screen
I don't know what im doing wrong
I made all by using guides and i think everithing is fine
Does it happens to somebody that can help me solve this problem?
I pass the dead line that i should upload my app and i'm really nervous
Please help me.
Thanks for all answers
The maps api key is based on the keystore sha1 hash and the package name. When you sign your apk, the sha1 hash changes (because you are signing with a different keystore).
Just add the sha1 hash of the new keystore, and the package name to a new line in the Key for Android apps (with certificates) section, under the API Access section in the Google Api Console. It's exlained here as well: https://developers.google.com/maps/documentation/android/start.
use your debug keystore to sign the apk or else you have genreate new api key with the sha1 the keystore which you want to export the project.

Categories

Resources