开发者

Re-installation failed due to different application signatures - Released app

My app is released and being used. I moved the development folder from my E: drive to C: drive and updated the various links to the libraries. Works great, but when I try and push it to the phone that has the previous version I get the above error.

As this is released I don't want the users to have to uninstall the app. There is a database where they have been storing info, and even though they are supposed all backup, someone will forget.

If I copy the APK to the phone, and then install it, it over writes the existing version without notice.

I seem to remember something like this when my workspace got corrupted and I seem to remember having to rename or delete a file or something.

the debug.keystore in the .android is the same file with a date from several months ago, so I don't think that is the problem.

Output end of the two APKs verifying jarsigner.exe, these are the only lines that are different that I can see.

   13821 Tue Apr 26 19:20:30 PDT 2011 META-INF/MANIFEST.MF
   13874 Tue Apr 26 19:20:30 PDT 2011 META-INF/CERT.SF
     955 Tue Apr 26 19:20:30 PDT 2011 META-INF/CERT.RSA


  14429 Tue Apr 26 14:04:54 PDT 2011 META-INF/MANIFEST.MF
   14482 Tue Apr 26 14:04:54 PDT 2011 META-I开发者_如何学编程NF/CERT.SF
     955 Tue Apr 26 14:04:54 PDT 2011 META-INF/CERT.RSA


Typically this only occurs if you changed the key you signed with OR you changed the values of android:sharedUserId, android:sharedUserLabel or application process in the AndroidManifest.xml.

If you did change any of those you are out of luck.

0

上一篇:

下一篇:

精彩评论

暂无评论...
验证码 换一张
取 消

最新问答

问答排行榜