darolla wrote:well, this tutorial works fine. but only one time. after updating your source code, and updating version name and version number in manifest.mf, deploying wont work anymore on g1.
sazabo wrote:Try just updating the version number
Sparkletron wrote:sazabo wrote:Try just updating the version number
That was already tried by darolla and I can confirm it has no effect whatsoever. The actual error is...
Package [my.package] signatures do not match the previously installed version; ignoring!
In the user data folder that we don't have access to, the G1 continues to store some reference to the file even *after* it's removed. And then it compares the digital sigs of every subsequent app with the original. If they don't match it rejects them. Now the question is: why don't the sigs match? Is there something about the formulation of that jarsigner command that creates a new sig each time? Certainly we are using the same keystores.
sazabo wrote:looks like the jarsigner -signed flag is not working correctly. I resigned the jar with the simplest variation and it worked.
Users browsing this forum: No registered users and 4 guests