Hello! I've been reminded lately how important it is to keep track of our release keystore for Android apps. This is the keystore that you create and use to sign your app before your publish it somewhere like Google Play or elsewhere. It also gets used when you publish an update to a currently published app, and it has to be the SAME release keystore! If you loose your keystore, or forget the password or keystore alias, then you can't sign your app, and you can't publish it. In the case of an update, Google won't see it as an update to an existing app, and you'll have to start from scratch. Scared? You should be, if you don't have your keystores in a safe place, backed up, and with all the relevant password/alias information either recorded somewhere or committed to memory! Not sure you understand what all this keystore talk is about? Check out this tutorial I wrote a while back: https://www.buzztouch.com/forum/thread.php?tid=84308A45D0AECFC6F296DDA The net of it all is this: your release keystore lets the world know that the app can be trusted (hopefully!), and who or what organization created it. It's akin to the iOS development and distribution certificates, but with Android, you get to generate the keystore yourself, instead of paying Apple to do it! Without your release keystore, you can't publish an app to the store, and you can't update an already published app. So, it's super important you remember where you put it, and the details associated with it. Before you leave this post, make sure your keystores are in order. You'll be glad you did! Mark

Yep. Mega important @GoNorthwest and perhaps a timely reminder with lots of new members. I have mine stored internally on pc also a copy on an external drive but this post just reminded me that I need to post a copy to dropbox also. You can never be too careful. Thanks

Maybe a way to help facilitate this. Like, for example, a "compile checklist" that includes a strategic way to REMIND folks to do this? Or...maybe a control panel "locker" that would allow people to upload them to a safe and secure place so they dont' get lost? The upload thing is more of a way to help the user remember to do this. Good thinking...as usual!!!

I know how important this is from personal experience. I had my Macbook stolen in a break in at our house but they also took the external hard drive that had all my backups. It doesn't bear thinking about the amount of work I have lost :( The thieves didn't take the charger lead or the Magic Mouse though.....so I don't think they knew how what they were stealing....thought it was just another laptop. So now I have a Box and Dropbox accounts for important backups! Geraldine

I created a mac automator script to zip up my keystores and throw them in a non-public section of my dropbox during the workflow. If I don't have to think about it, I don't have to worry about it. Thanks for the reminders. No one takes them seriously until disaster strikes. This is one that's too easy and too important to ignore. Cheers! -- Smug

:-) That is all I am going to write!! P.s I was a culprit of losing my keystore or the file became corrupted. Either way, back them up and keep them safe. Thanks, Mark.

Great advice @GoNorthWest! I've had my struggles understanding the difference between signing and maps, but I do understand now. David @buzztouch: I think a "locker" would be great! LA

Dropboxed and burned to CD/DVD is also good back-up in case of hardware failure. Love the secure locker idea or an extra folder on the BT File manager for these and .certs and .p12, etc...

Good reminder! I store mine on lastpass, and pull them up every time I need them.