Package signatures do not match the previously installed version
You need to uninstall it because you are using a different signature than the original. If it is not working it might be because it is still installed for another user on the device. To completely uninstall, go to Settings -> Apps -> HAgnostic News -> Options (the three dots on top right) -> Uninstall for all users
How to fix signatures do not match previously installed version error?
For people still facing this issue, yes this issue is still unresolvable to this date. At least I have found out why the issue happens, which is apparently because when I remove an app, Huawei asks whether I would also want to remove the app's data or not. I answer "no". And once you answer "no", you'll never be able to reinstall that app on that device ever again, because of the residue of the app data on your device. And I have tried my best to remove any residue by any means, I still cannot reinstall the app.
Only one cure works: reset factory settings. I did this and now I can reinstall the app. Of course, that means the data will be lost. But at least there's a Huawei backup app, so there's that.
INSTALL_FAILED_UPDATE_INCOMPATIBLE: Package signatures do not match the previously installed version; ignoring
I met the same error today.And I found thishttp://blog.bihe0832.com/android-v2-issue.html
.It's in Chinese.The key points describe below:
After package your apk file, unzip it,check the file
META-INF/ANY-NAME.SF.I sign the apk withjarsigner
command line
tool.I found that thealias
putted after the jar-file when exec the
jarsigner
, will used as theANY-NAME
.Then open the ANY-NAME.SF, if
you found a line ofX-Android-APK-Signed: 2
,That's the cause of the
error.Resign your apk,if the line of code gone, the apk will be
installed success.
Manually installing an updated APK fails with signatures do not match the previously installed version
Yes It is possible if somehow your old application is not removed 100% or its data is not removed.
Try:
adb uninstall "com.yourapp.yourapp"
If you don't know exactly what to put as replacement for "com.yourapp.yourapp", then you just open Android studio, Run your app while it is connected to a device and then look at Debug window.
It says:
Waiting for device.
Target device: samsung-sm_t531-xxxxxxxxx
Uploading file
local path: C:\Users\myapp\app\build\outputs\apk\myapp.apk
remote path: /data/local/tmp/com.myapp.myapp
Installing com.myapp.myapp
DEVICE SHELL COMMAND: pm install -r "/data/local/tmp/com.myapp.myapp"
pkg: /data/local/tmp/com.myapp.myapp
Success
com.myapp.myapp in this case is the name of the package you must use to uninstall.
Cannot install newer version on android device
This means, that the two APKs are signed with different signing keys.
If you try to install a debug version, the APK is signed with a debug key. So it is normal that the installation will fail.
In order to test the update of your app, either create a release version of your app (e.g. by selecting "release" from the "Build variants" tab. Or add the signing release configurations to your debug build variant in the app module's build.gradle
file.
Installation failed with message INSTALL_FAILED_UPDATE_INCOMPATIBLE: Package signatures do not match the previously installed version
There are two possibilities I can think of
- You use Google Play App Signing. If you use Google Play App Signing then the signature in apps coming from Google Play will always be different to the app coming from your IDE. The only way you can get the update to work is to update the app from Google Play. The best way to do this during development is to use an "Internal test track". Google launched these at Google I/O this year and they let you update your app in seconds from Google Play. So when you have an update, don't install from your IDE, upload to Google Play internal test track, republish, and then update from Google Play. It is really quick.
- You don't use Google Play App Signing, but you are trying to install your debug build instead of your release/production build. Make sure you are building the production release APK, so it is signed with the same key as the one uploaded to Google Play.
Related Topics
Android Studio Could Not Find Any Version That Matches Com.Android.Support:Appcompat-V7:+
Speechrecognizer Causes Anr... I Need Help with Android Speech API
No Resource Found That Matches The Given Name '@Style/ Theme.Holo.Light.Darkactionbar'
Creating a Seterror() for The Spinner
Android Sqlitedatabase Query with Like
How to Import an Existing Project from Github into Android Studio
Gradle Android Build for Different Processor Architectures
Add Margin Between a Radiobutton and Its Label in Android
Handle Screen Orientation Changes When There Are Asynctasks Running
How to Add a View Programmatically to Relativelayout
How to Set a Fragment Tag by Code
How to Change Android:Windowsoftinputmode Value from Java Class
Android Sdk Install: Java Se Development Kit (Jdk) Not Found
Mobile Chrome Fires Resize Event on Scroll
Hide Tablayout on Scroll of Content Instead of Toolbar