Hello

I know there have been countless posts about people forgetting their
passwords or losing their keystores, but for me it's different: I
still have the old keystore file and I do have the password. I tried
jarsigner -verify with -storepass and -keystore set for both, my old
signed apk and my new one, and in both cases the jar gets verified.
When I try to upload however, I get the "The apk must be signed with
at least one certificate in common with the previous version."
How can that be? I didn't create a new keystore since...

An odd thing is, that if I enable -certs I get this message:
[certificate is valid from 4/16/09 9:53 AM to 6/5/91 9:53 AM]

1991!! could that be the problem? I did read about the requirements of
expirations and I remember being within that limit. I couldn't even
have uploaded my app had it expired in the past since there's this 30
years something restriction.... how can that happen?

Does anyone have an idea of what else could have gone wrong? Or can
anyone tell me how I can properly compare the certificate between the
2 apks myself.
thanks
yannick

-- 
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

Reply via email to