Reputation: 21
Edit: solved by myself 10 minutes after asking (see answer; I leave the question here for people with the same problem and I'll close it as soon as I can answer it by myself)
Released app with wrong maps api key and now it's impossible to solve this problem for people who already downloaded the app
Setup: Android App (Api Level 8+), Google Maps V2, SupportMapFragment (com.google.android.gms.maps.SupportMapFragment)
Problem: I released an update (let's call it V1.0.1) for my app, which had the debug (hence wrong) maps api key in it's manifest.
Those, who had the previous version on their phone (V1.0) could install the update without any problem (map was shown). However, those who installed the app for the first time (so V1.0.1 was their first install), had a gray map (since it's the wrong api key). No Problem - I thought - let's make an V1.0.2 with the correct api key. Lets assume, everybody updated to Version 1.0.2, we now have three groups. People with first install:
Android seems to cache the maps api key from the first install. Is it possible to "reset" this, so I don't have to tell all people who installed with V1.0.1 to delete and reinstall?
This seems to be a bug in the google maps concept since it's not even possible to declare an "debug api key" and a seperate "release api key"
Upvotes: 0
Views: 364
Reputation: 21
Well, 10 minutes after writing this post, I figured it out by myself (after five days of searching and googling): I used two different api keys (one for development, one for the release). At the end: that's stupid, since you can have several app hashes attached to one key. Hence that's the solution, just added on code.google.com/apis/console the release hash to the development api key (for backwards compatibility) and the development hash to the release api key (for easier development). I hope, this helps somebody with the same problem.
Upvotes: 2