Apps Getting grey grid on google maps app

[kodiak211]

I created a google maps app. I have been using the debug md5 fingerprint to test my app as I built it. It worked fine. Now that I'm ready to publish, I'm having a problem with the nondebug md5 fingerprint I need to publish with. I'll go step by step with what I've done. I right click my app in eclipse, then go down to android tools > export signed application package. It pops up a window. I see my app name i hit next. keystore selection> create new> C:\AndroidApp\MapKey> create passwords for it hit next. Key creation> create my alias name. lets say mapalias> give it the same password as the keystore. Give it a validity of 1000> insert my name. hit next. destnation and key/certificate check> C:\AndroidApp\MyGoogleMaps.apk > hit finished. After that i open up cmd, I'm on windows 7. I type> keytool -list -v -alias mapalias -keystore C:\AndroidApp\MapKey -storepass mypass -keypass mypass. It generates the md5 code i need. I go to the website to register the md5 code. get the code i need to use on my android:apiKey="ofhsjfjfjmmmmmdnjjffmmf". Run it on the emulator and my phones. I get a grey screen with no map coming up. Theres something I'm missing hear... Please help if you can. Be clear please. I'm a newbe.

 

[wubbzy]

one of the three that I've encountered

- Wrong api or map key. Remember map key is different.

-- OR --

- You're signing with wrong key i.e. your Map Key is production but you're signing your APK using debug key store or maybe other way around (this is most common problem BTW). If you have put your real key in XML/code, then you need to use File->Export from eclipse to create APK and to use production key.

-- AND --

- Irrespective of both points above to project->clean (select your project), this helps sometimes as XML changes do not trigger full build, hence leaving project in inconsistent state.

Hope this helps.

 

[kodiak211]

one of the three that I've encountered

- Wrong api or map key. Remember map key is different.

-- OR --

- You're signing with wrong key i.e. your Map Key is production but you're signing your APK using debug key store or maybe other way around (this is most common problem BTW). If you have put your real key in XML/code, then you need to use File->Export from eclipse to create APK and to use production key.

-- AND --

- Irrespective of both points above to project->clean (select your project), this helps sometimes as XML changes do not trigger full build, hence leaving project in inconsistent state.

Hope this helps.

(If you have put your real key in XML/code, then you need to use File->Export from eclipse to create APK and to use production key.) Son of a B**ch i think that worked. Cuzzo I've been on this problem since 2 in the morning yesterday. Went to bed till 12 and been on it till now. witch is 3:47AM and I got to be at work in 4 hours...lol I've been bent on this all day. And at a complete halt on this project... How do you know if its running the right md5 and not the debug version? If I go to publish will it inform me that I'm using the debug version? When I did this my android:apiKey="0pn_*******************************" wasn't the debug md5 fingerprint. Is that a indicator? I got to thank you. Thanks man... I mean that!!!