I'm 3 hours in on trying to find the keystore file on my Mac to get the MD5 fingerprint. The directions Google provides are spotty at best (as compared to others) Anyone got any ideas? Thanks, Bruce

Hi Bruce, I'm not sure what you're looking for? Maybe you're trying to do something other than use the built-in map feature. If so, point me to a URL, lend some insights, something with a little more details about the Google API you're trying to use that requires you to find the MD5 fingerprint of something on your mac ;-)

Ok, I can do that ;-) In order to get the maps to work in Android I need to get 2 google map API keys. I've read your instructions very carefully. The first thing google does is ask you to get the MD5 fingerprint before you can get the API keys, well I can't find it anywhere. I'm supposed to have a .android folder (supposedly) at the root directory, which I don't have. Nor do I have a keystore file on my computer. I have downloaded the Android SDK and Eclipse. I've updated all the files in Eclipse and have downloaded all the extras. The directions google gives leave out the instructions for getting the fingerprint. They just tell you to get it done, not HOW to get it done. Does that make more sense? Thanks, Bruce

I struggled with the same problem. You must use keytool.exe found in your \Jav\jre6\bin\ directory. Here is the command I used in a DOS cmd window to generate the MD5 fingerprint: keytool.exe -list -alias xxxcertkey -keystore C:\users\jack\.android\xxxcertkey.keystore -storepass xxx1 -keypass xxx2 This gave me a fingerprint that looks like: E6:6E:F7:B8:56:FB:4E:6C:F7:85:09:D8:4D:2A:C4:30 Go to http://code.google.com/android/maps-api-signup.html and enter your fingerprint. You will receive the debug key. See: http://developer.android.com/guide/publishing/app-signing.html for instruction on generating the private key.

I've got a Mac. I've looked online and it seems I'm missing a directory. I can't find much on the web about the Mac and this particular problem. I'll just have to keep looking. Thank you for your time, bruce

It does appear you are missing the .android directory. This blog may help (see second solution): http://android-pro.blogspot.com/2010/08/android-error-error-generating-final.html

Yeah, that seems like a great idea but the following directory does not exist on the 2 macs I own inside the Java\jre6\bin folder in Mac OS or Linux. This is what I can't figure out. I'm a pretty advanced user too. I take care of about 50 Mac's at a local school and for the past 10 years I've done video production and engineered workstations. All that experience is doing me no good at the moment. This one is stumping me. I've got all the pieces installed (or so it appears) but I can't figure out why I don't have the directories or the files I need. On top of that I can't find anything that will tell me how to create or get those files anywhere on the web... Yet! Thanks Again, Bruce

So, I just re-created some API keys to see how the process works on this Mac. I didn't do anything other than: a) Open up the Terminal App b) Type this: keytool -list -alias buzztouch_release_keystore -keystore /Users/davidbook/Documents/android_cert_keystore/buzztouch_release_keystore -storepass yourpassword -keypass yourpassword Enter this all on the same line, do not press enter between any entries. The directory path (it's long) will be the path on your machine to the folder you want to save the results. The your password can be anything you want -don't forget the password you use. c) press enter When I look in the folder, in my case buzztouch_release_keystore there is a file without an extenstion that the tool created when running the command. Can you get this far or is your machine not allowing you to run the keytool from the command line. I didn't have to dig around for anything, just ran the command, that's it.

Here's what I got back after typing all that in: Keystore file does not exist: /Users/brucefraser/Documents/android_cert_keystore/buzztouch_release_keystore

Did you create a folder called buzztouch_release_keystore - probably not. Create a folder called trailman_keystore or something strategic. This is the folder you will be saving your API keys to. Create the folder, then use it's name in the command where I used buzztouch_release_keystore I have a buzztouch_release_keystore and a buzztouch_debug_keystore folder on my machine. When I run the command for debug, I use the debug folder, when I run the command for release, I use the release folder.

Still didn't work. Keystore file does not exist: /Users/brucefraser/Documents/sedonavortex_release_keystore What is supposed to happen? Thank You, Bruce

Ok, it DOES sound like the tool is trying to work, negating any reason to try and find something on your machine that you mentioned in an early post. I'm still not entirely sure what's happening here but it's gotta be something easy, something we are overlooking. It sounds to me like a matter of finding where your keystore is. This is a fancy name for the directory. I thought I setup the keystore when I installed the Android SDK on this machine, it's looking like I didn't and Android / Eclipse did it for me (so much for my memory). See this: http://eagle.phys.utk.edu/guidry/android/apiKey.html We'll stick with this until we get it sorted out ;-)

I'll be away from my desk most of the afternoon but will re-visit this when I return.

It looks to me like not having the .android folder anywhere on my system could be the problem. Nor are any of the other folders I've seen mentioned in the articles I've read. I'll go through the installation process again and see what happens. Bruce

Hmmmm... I found the .android folder today. It was not there yesterday. I can see a debug.keystore file and a default.keyset file. Does that help? b

ok got it! After locating the .android folder and removing the $ symbol from the instructions you sent. I now have a fingerprint. Thanks so much for taking the time to help! You Rock! Bruce

ok got it! After locating the .android folder and removing the $ symbol from the instructions you sent. I now have a fingerprint. Thanks so much for taking the time to help! You Rock! Bruce

The API keys are exactly the same. Is that correct or am I doing something else wrong? b

Now I'm getting the error message in Eclipse when following the video on how to compile the source code: 2011-01-12 14:30:16 - Sedona Vortex AndroidManifest.xml file missing! I can see the file in Eclipse and in the folder in Documents. b

Forget my last post. What's happening now is Eclipse is crashing every time I create a virtual device. As soon as I click the create AVD the rainbow ball of death spins forever. i chose Google Apis (Google Inc.) - API Level 4 and set the SD Card to 32000. Default Skin. Is it me or is the universe conspiring against me? ;-) b

Waiting for the SD card to be at full size was the ticket. Everything appears to be working now. The only thing left (for now ;-) ) is I get the same API key when I apply for 2. Thanks for all your help. bruce

You're going to be an Android expert before too long - what a road you've travelled! So, yeah, you should have two different Goole Map API keys, one for the Debug and one for Release. I'm thinking at this point you've read 100 pages of info on how to create them so I'm sure what else to lend. The info you already read here http://code.google.com/android/add-ons/google-apis/mapkey.html explains the differences. Can't beleive you've stuck with it this long, most would have said screw-it by now.

I'm ready to give up. I have the same problem as trailman. and many others. You might want to rethink the whole make maps an default part of this thing

@mindog: We agree, the maps does add some difficulty when compiling your project in Android - bummer. The iOS counterpart is sooooo much smoother and easier to implement without any programming skill. If you're unable to understand how to get the maps to work, you may indeed choose to give up, up to you. However, thousands of folks have successfully implemented mapping functionality in their apps without experiencing the difficulties experienced by a few. For this reason, we will continue to do the best we can to help, continue to improve and make it simpler, and continue to listen to feedback like this. Thank you TONS for your perspective - it's very important to us.

David, Sorry if I struck a nerve. Not looking a gift horse in the mouth, just seems logical if you spend as much time as you appear to answering questions about this problem, making it optional would eliminate any of that. To your point, EVERYTHING is easier and smoother on IOS. I have built several advanced apps from scratch without any issues. Indeed this seems to be a lack on Google's part for clearly explaining the whole keystore issue. I have done all that you have suggested with trailman, exact same issue with no luck. It's all due to this keystore issue when I have no need for any maps functionality at all, I think you can understand the frustration there. :-)

totally get it - no nerves - no worries - really. It's a huge priority to get the maps / facebook / other JUNK that is required in the android version REMOVED so it's not even part of the project unless map-folks want it. Just a matter of balanacing all the goings on. Thanks for caring - good stuff.

What if you hired someone to do it for you? I think any unix guru could figure it out in less than 15 minutes. When I do more apps I hope I can remember how i did it... ;-)

Making progress I was able to generate an MD5 fingerprint but when I submit to Google I get it's invalid because no password was set. LOL, Good thing I'm already bald. No pulling my hair out. lol Too pigheaded to hire someone. I'll break this sucker or die trying.

David, Any ideas here? If I put keytool -list -keystore ~/.android/debug.keystore into the terminal, and leave the password blank at Enter keystore password: i get an MD5 fingerprint but the message: ***************** WARNING WARNING WARNING ***************** * The integrity of the information stored in your keystore * * has NOT been verified! In order to verify its integrity, * * you must provide your keystore password. * ***************** WARNING WARNING WARNING ***************** if I use your _keystore -storepass yourpassword -keypass yourpassword on the end I get a file does not exist error. If I try to find the folder .android It's invisible/hidden but if I go to file open in Eclipse I see it. Any clues?

David, Any ideas here? If I put keytool -list -keystore ~/.android/debug.keystore into the terminal, and leave the password blank at Enter keystore password: i get an MD5 fingerprint but the message: ***************** WARNING WARNING WARNING ***************** * The integrity of the information stored in your keystore * * has NOT been verified! In order to verify its integrity, * * you must provide your keystore password. * ***************** WARNING WARNING WARNING ***************** if I use your _keystore -storepass yourpassword -keypass yourpassword on the end I get a file does not exist error. If I try to find the folder .android It's invisible/hidden but if I go to file open in Eclipse I see it. Any clues?

i get the same as Minddog.. please help.. i've been trying to sort this Google Maps for 2 days now... such a pain Regards Adam

http://developer.android.com/guide/publishing/app-signing.html Read the signing in Debug section

Yes, Google Maps are a pain. In face, the entire Android process is a pain when compared to the Apple process (my opinion). I'm not sure how else to help. The videos and the dozens of other forum posts about this cover most of it but not all of it. Feel free to post your struggles if they continue and we'll continue to do what we can.

Use the command: keytool -list -keystore ~/.android/debug.keystore and then, enter the password: android - copy the MD5 and get your apiKey in Google. Good luck.

Adam, I don't remember now all the crap I had to go through to get this to work, but I clearly remember the lack of information was on Google, not Buzztouch. I was able to get it working with the help of this forum and lots of painful trial and error. I remember one of the problems I had was the MD5 had a prefix that is not needed, xx or something. I kept pasting that in just the way Google provided it, but it never worked until I dropped the prefix.

I had the same issue. I can't remember too well how I got it all to work. Each person has different issues to overcome to get the damn thing to work.

Maybe the best keytool help video yet! http://www.youtube.com/watch?v=vgr4l1nsFdU&feature=related