Georgios Galyfos wrote: > Hello, this is very urgent, as I just found out that the maps are not > showing on my app, now that I signed it, with the map api key i was > using so far. > > here it says: > > http://code.google.com/android/add-ons/google-apis/mapkey.html#finalsteps > > Note that, when you are ready to publish your application, you must get > a Maps API Key that is based on the certificate that you will use to > sign the application for release. You must then change the Maps API Key > strings referenced by all of your MapView elements, so that they > reference the new Key. > > Can anyone please provide details on this one, please??
Those *are* the details. Somewhere, you have a layout file. It contains a MapView element. That MapView element has an android:apiKey attribute. That attribute's value is a really ugly string. You got that really ugly string from Google via: http://code.google.com/android/add-ons/google-apis/mapkey.html However, you did so for your debug key. You are now signing with your production key. The debug key is not the production key. The Maps API key is tied to the signing key. So: -- Sign with the debug key, use a Maps API key created from your debug key -- Sign with the production key, use a Maps API key created from your production key So, go get yourself a fresh really ugly string based on your production key's fingerprint, as described at the page I linked to above. Odds are, that will clear up your problem. -- Mark Murphy (a Commons Guy) http://commonsware.com | http://twitter.com/commonsguy _Android Programming Tutorials_ Version 1.0 In Print! --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
