Transitioning Android Dev From Linux To Windows: Toolchain Signes Apk Differently?

I have been developing my Android App on Linux and Eclipse for a year now. Decided to switch to windows for a number of reasons. Jumped through all the hoops, and now have my App b

Solution 1:

Binary diffs will reveal nothing. Use jarsigner to check the differences in the actual signatures:

jarsigner -verify -verbose -certs app.apk

Most likely the reason for your problem is that the default digest algorithm for jarsigner has been changed to SHA256 in Java 7, if you specify SHA1 explicitly with -digestalg SHA1 you should get the same signature (or just use Java 6). Android, and the Market, compare the signature as a binary blob, and really don't care about the actual certificate at this point, that is why it complains. Technically, if it is signed with the same key by the same person (certificate), it should be considered a valid signature. Not letting you change the digest algorithm to a more secure one should be considered a bug.

BTW, I don't think ADT officially supports Java 7 yet.

Solution 2:

DUH!!! I made a stupid mistake with my revision control and was using the wrong version of my key store ... ignore this!