It's 2016 now. Is this still an (unnecessary) problem?

It's ridiculous if you think about it - and it causes people to do things 
like emailing the private key to themselves (for real - email!).

Apple doesn't have this problem because they store the publish keys, and 
issue a separate key for developers which can be regenerated and revoked at 
the server - this is simply better.

Kevin N.



On Tuesday, March 8, 2011 at 9:45:09 AM UTC-5, hoyski wrote:
>
> I had a frantic and terrifying couple of hours the other night looking 
> for my keystore file. A few months ago I restructured my workspace and 
> source directories and unwittingly deleted the keystore used to sign 
> my app, something I was completely unaware of until I went to sign the 
> latest release of my app. 
>
> I knew all of the inputs I'd used to create the keystore so I thought 
> there may be some way to recreate it. Searching Google I found that 
> the answers fell into two categories: "Dude, you're screwed" and 
> "Dude, you're [expletive deleted]." 
>
> Luckily my tale has a happy ending. I'd temporarily used a different 
> machine for development and I found a copy of my keystore on that 
> machine. Suffice to say, I now have copies of my keystore 
> *everywhere*. I may even print out a copy of a hexdump as the ultimate 
> hardcopy backup. 
>
> Just figured I'd share this in the hopes that it may spur others to do 
> what I should have done from the beginning. 
>
> - Dave 
>

-- 
You received this message because you are subscribed to the Google Groups 
"Android Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to android-developers+unsubscr...@googlegroups.com.
To post to this group, send email to android-developers@googlegroups.com.
Visit this group at https://groups.google.com/group/android-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/android-developers/e54d0bc5-117e-4704-a397-d281e4301eca%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to