Cause and resolution of "a packet with the same name with signature violation" appears on Android phone

http://blog.csdn.net/dyllove98/article/details/8830264

If you are not a developer: if you update an earlier version of the software on Android, install to the last step: you have installed a packet with the same name with a signature violation, and then the installation fails. This is because the old version of the software signature information and the new version of the inconsistency caused. You can uninstall this software and install the new version of the software.

If it cannot be uninstalled, it may not be possible to uninstall the mobile phone (PAD) before it is released. If this is the case, you can try the "root" system, then uninstall the old version of the software and install it.

If you are a developer, the problem may be that the older version is automatically published to the emulator using Eclipse, and Eclipse is automatically released using a test signature that is not one of your formally packaged signatures. (This problem usually occurs in the test auto-update function, hehe). To continue testing Automatic Updates, the solution is simple, manually remove the old version of the software (the one that Eclipse automatically installs), and then use the ADB tool to install the old version and then test the new version.

The installation code for Automatic Updates is typically called intent installation

New Intent (Intent.action_view); I.setdataandtype (Uri.parse ("file://" + apkfile.tostring ()), "application/ Vnd.android.package-archive "); mcontext.startactivity (i); 

Maybe you are slightly different from this, don't worry, nothing, the problem is not here.

Cause and resolution of "a packet with the same name with signature violation" appears on Android phone