haha; yeah...i've put my latest one in subversion.... so anybody have any other ideas? I feel badly cause I'm really cheating the users of my app that won't get the new functionality that i built....kinds sucks.
On Sep 24, 3:52 pm, Streets Of Boston <[email protected]> wrote: > I know it's too late now, but after you create a keystore, back it up! > If it gets corrupted or lost, you can restore it. > > On Sep 24, 11:19 am, CaseyB <[email protected]> wrote: > > > I had the same problem. It happened right around the time I updated > > to the 1.5 SDK. I also updated Java around the same time. I don't > > know if either of those had anything to do with it but something > > happened. I tried for a day or so to figure out how to salvage the > > keystore but ended up just deleting it and creating a new one. This > > lead to big problems when updating apps in the Android Market. It > > won't let you upload an update that has been signed with a different > > certificate. That's what I'm dealing with now. > > > On Sep 23, 9:40 pm, rde8026 <[email protected]> wrote: > > > > Hello, > > > > I'm having an issue with my keystore. i crated it a while back and > > > now I want to provide an update. I know I'm providing the correct > > > password but I keep getting the error message that says the keystore > > > has beentamperedwith or the password is incorrect... Is it possible > > > to generate a new keystore? Has anyone else seen this issue? Is > > > there a way I can fix this....any guidance would be awesome..- Hide > > > quoted text - > > > - Show quoted text - --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
