Reputation: 1848
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
Upvotes: 3
Views: 2287
Reputation: 300
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.
Upvotes: 0
Reputation: 65
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 ...
Upvotes: 1
Reputation: 15533
Check your manifest file, I guess you've forgotten to set your release map api key there while exporting with your release key?
Upvotes: 1