locked
INSTALL_FAILED_UPDATE_INCOMPATIBLE RRS feed

  • Question

  • User1038 posted

    I get this error each time I try to debug my latest version on my LG phone. My app used to work on the LG and it is running fine on a Google Nexus 7.

    Below is the error from Visual Studio:

    Xamarin.AndroidTools.AndroidDeploymentException: 
    InternalError ---> Mono.AndroidTools.InstallFailedException: Failure
    [INSTALL_FAILED_UPDATE_INCOMPATIBLE]
    at Mono.AndroidTools.Internal.AdbOutputParsing.CheckInstallSuccess(String output, String packageName)
    at Mono.AndroidTools.AndroidDevice.<>c__DisplayClass2a.<InstallPackage>b__29(Task`1 t)
    at System.Threading.Tasks.ContinuationTaskFromResultTask`1.InnerInvoke()
    at System.Threading.Tasks.Task.Execute()
    --- End of inner exception stack trace ---
    at Xamarin.AndroidTools.AndroidDeploySession.RunLogged(CancellationToken token)
    at Xamarin.AndroidTools.AndroidDeploySession.Start(CancellationToken token)
    

    Any idea of the cause or how get app to install?

    Monday, September 30, 2013 10:04 PM

All replies

  • User35 posted

    I'll see this type of error when I'm developing on my device. Then I go to install a release version via TestFlight or adb and this message happens. A lot of the time this happens because your debug version is signed with a different key than the release version. Android detects this and gets angry.

    You get rid of it by uninstalling the older version of your application. YOu might have to go into Settings...Apps, and scroll down to your application and then delete it from there. Once you've deleted your application it should install normally.

    Then when you

    Monday, September 30, 2013 11:32 PM
  • User1038 posted

    That would make sense except I don't have any version installed on the device. I re-checked app manager and the app is not installed.

    Tuesday, October 1, 2013 1:12 AM
  • User1038 posted

    The problem seemed to be that a "ghost" copy of my app still existed on the device (probably just a file or two), so there was no app icon and it was not listed as an installed app.

    To fix it I reinstalled the production app from the external SD and then uninstalled it (using AppInstaller which is great if you haven't tried it).

    Now the debugger is able to install the debug version without incident.

    Tuesday, October 1, 2013 8:30 PM
  • User46866 posted

    Had the same issue when i changed development machines. I checked out the code from VS online for my android project on the new machine - tried to debug - and got the error. The application was not visible on the device anymore so i re-deployed from the old machine, uninstalled it, then deployed from the new machine without any issues.

    Monday, October 27, 2014 1:31 PM
  • User2029 posted

    Delete your existing app. It will not be listed under applications with the display name nor have a launch icon. You will find it under Applications with its package name instead. It always is there. Uninstall the package and deploy your new version normally.

    This is a very old "limitation".

    Tuesday, October 28, 2014 5:46 AM
  • User7916 posted

    Happened to me too when switching dev machines. Softlion's fix worked.

    Wednesday, January 21, 2015 12:38 PM
  • User40038 posted

    @softlion You're a life saver, thank you!

    Monday, May 25, 2015 7:20 PM
  • User64810 posted

    I had an identical issue here today, after some head scratching I traced it to the fact I'd intentionally enabled 'Preserve application data/cache on device between deploys' under Tools -> Options -> Xamarin -> Android Settings: Emulator Device/Debugging. At next next deploy the app appeared to be uninstalled but when checking in Task Manager it showed it was still installed with a size of ~60Kb. Uninstalling manually then solved the issue and I was able to deploy successfully and preserve my settings too.

    Cheers

    Saturday, June 6, 2015 8:56 AM
  • User109338 posted

    @Tom Opgenorth , you rock . It works :smile:

    Tuesday, July 7, 2015 6:36 AM
  • User130023 posted

    The solution given by Benjamin worked for me. Thank you.

    Benjamin Mayrargue October 2014 Delete your existing app. It will not be listed under applications with the display name nor have a launch icon. You will find it under Applications with its package name instead. It always is there. Uninstall the package and deploy your new version normally.

    This is a very old "limitation".

    Wednesday, July 8, 2015 2:37 PM
  • User138614 posted

    Happened to me today and left me confused. The thing is that I:

    1) Installed APK of my App from different source.

    2) Then I wanted to install it from Xamarin Studio.

    3) Previous App got uninstalled but new build did not get installed and left me with error:

    Deployment failed because of an internal error: Failure [INSTALLFAILEDUPDATE_INCOMPATIBLE]

    Solution:

    1) Install on your device the previous APK again.

    2) Properly uninstall it from your device.

    3) Try to install the new build through Xamarin Studio.

    It should work now :)

    Wednesday, August 5, 2015 3:37 PM
  • User140120 posted

    Just follow any of the solution that will work 1.give Build to project 2.Clean Project 3.Check your phone setting-->App-->got to All categories-->Find out the App that you installed uninstall for all users(In new phones like Lollipop version) or else normal uninstall

    4.Still one kind of file like com.yourporoject.Appname will be there uninstall that one tooo

    run again

    Friday, September 18, 2015 9:32 AM
  • User133193 posted

    An alternate solution is to run the command i.e. adb uninstall com.theircompany.packagename from android command prompt located at below path: "AppData\Local\Android\android-sdk\build-tools"

    Tuesday, November 24, 2015 10:55 AM
  • User180261 posted

    @softlion said: Delete your existing app. It will not be listed under applications with the display name nor have a launch icon. You will find it under Applications with its package name instead. It always is there. Uninstall the package and deploy your new version normally.

    This is a very old "limitation".

    Thanks @softlion

    Friday, March 11, 2016 2:48 PM
  • User166736 posted

    Hai Jakub Holovsky,

    Thanks for this solution its now work on my simulator device from the xamarin studio.

    Thank you... Praveen

    Tuesday, March 29, 2016 8:02 AM
  • User133044 posted

    Android Studio and Eclipse prompt to remove and replace the app if the signature doesn't match. XS and VS need to do the same.

    Thursday, March 31, 2016 1:56 AM
  • User124213 posted

    it never happen to me on Xamarin Studio, after switch to Visual Studio. it happen all the time. (paid more moeney to get more trouble......)

    Monday, April 18, 2016 2:56 AM
  • User29221 posted

    if happen on simulator you can factory reset the image.

    Thursday, May 5, 2016 10:54 AM
  • User22834 posted

    You'll also get this error if you don't have your keystore set correctly in Android Package Signing.

    Monday, May 9, 2016 3:59 AM
  • User111866 posted

    @softlion said: Delete your existing app. It will not be listed under applications with the display name nor have a launch icon. You will find it under Applications with its package name instead. It always is there. Uninstall the package and deploy your new version normally.

    This is a very old "limitation".

    THANK YOU, @softlion - that was extremely helpful.

    Tuesday, June 28, 2016 6:27 PM
  • User217632 posted

    @MehulTheXammer Thank you for your solution. It works for me.

    Sunday, July 3, 2016 9:30 AM
  • User240301 posted

    First off I like to thank all for the hints and tips thus far, the issue has creeped in for me when on VS 2015 update 3; I it took me a couple of days to solve. So hopefully this post,will help others:

    I initially installed one of these components to test/use in my solution via nuget: https://www.nuget.org/packages/Xamarin.Android.Support.v4/ https://www.nuget.org/packages/Xamarin.Android.Support.Design/ https://www.nuget.org/packages/Xamarin.Android.Support.v7.AppCompat/ https://www.nuget.org/packages/Xamarin.Android.Support.v7.CardView/ https://www.nuget.org/packages/Xamarin.Android.Support.v7.MediaRouter/

    However if you look closely at the release at the bottom of the page its latest release = 23.4.0 Then when installing Xamarin.Froms https://www.nuget.org/packages/Xamarin.Forms/ there are lots of failures because again looking at the bottom of the page:

    Dependencies MonoAndroid 1.0 Xamarin.Android.Support.v4 (= 23.3.0) Xamarin.Android.Support.Design (= 23.3.0) Xamarin.Android.Support.v7.AppCompat (= 23.3.0) Xamarin.Android.Support.v7.CardView (= 23.3.0) Xamarin.Android.Support.v7.MediaRouter (= 23.3.0)

    So it needs to have specifically version 23.3.0 and not the latest version 23.4.0, so uninstall each of these separate components manually and then only install Xamarin.Froms targeting release 23.3.0. Unfortunately somewhere along the line I also undated my SDK( to 24 thinking it needed a later version to help) and when having VS and SDK manager doing updates (via nuget or other) the android sdk folder is cleared: https://forums.xamarin.com/discussion/43688/android-sdk-manager-and-avd-will-not-open-neither-will-my-xaml-layouts this solution solves that problem.

    Then I started the SDK manager and noticed that I now have the latest SDK (25.1) which is fine but then this issue started popping up https://forums.xamarin.com/discussion/20816/error-building-project-with-google-play-services and my solution does not build. However this in itself was a red herring. (I actually ended up doing reinstall of VS and then the SDK manager, which does not solve anything)

    What worked for me was manually uninstalling the app in the applications (as all the helpful people pointed out), and then also firing up adb and then running uninstall returned a successful response. Running it again actually then only gave the failure response I was hoping for, to know it was truly off the device. So somewhere in the device(I tested on both virtual and physical devices using kit kat, lollipop and marshmallow ) there was still a ghost copy of the application looming.

    NB: I also tried doing a factory reset, but did not remove the application/Allow the application to redeploy to the device... it seems really only adb removes the application completely.

    In summary: Check Xamarin.Froms release version before installing/reinstalling. I would also check/confirm if the adb uninstall process returns a success or failure response, to make sure the original app is really gone; before looking elsewhere for a potential problem.

    Regards, W

    Friday, July 8, 2016 6:37 AM
  • User192302 posted

    Ok Guys

    This is a very STUPID error and time wasting!!

    I tried all most everything to delete it from my LG G3. But this helped:

    Run the following command from the Android console: "adb uninstall com.theircompany.packagename"

    This should allow you to uninstall the app manually from the device without having to do a factory reset.

    Sunday, July 10, 2016 4:27 PM
  • User214389 posted

    Great job, thanks

    Wednesday, July 13, 2016 3:07 PM
  • User158361 posted

    adb uninstall com.theircompany.packagename

    worked for me too - Thanks.

    Monday, August 1, 2016 3:36 PM
  • User29221 posted

    The solution is to reinstall APK, then in Setings --> Application uninstall it.

    Tuesday, August 2, 2016 10:48 AM
  • User29256 posted

    @AmjadAzizi10 said: Ok Guys

    This is a very STUPID error and time wasting!!

    I tried all most everything to delete it from my LG G3. But this helped:

    Run the following command from the Android console: "adb uninstall com.theircompany.packagename"

    This should allow you to uninstall the app manually from the device without having to do a factory reset.

    I agree, this finally worked for me!

    Tuesday, August 9, 2016 6:47 PM
  • User148199 posted

    @PaulKeefe said: The problem seemed to be that a "ghost" copy of my app still existed on the device (probably just a file or two), so there was no app icon and it was not listed as an installed app.

    To fix it I reinstalled the production app from the external SD and then uninstalled it (using AppInstaller which is great if you haven't tried it).

    Now the debugger is able to install the debug version without incident.

    You are my hero.

    Thursday, August 11, 2016 8:25 AM
  • User66686 posted

    In my case even when i had uninstalled the app, the error was still appeared.

    Probably something wrong happened during the last deployment (in the current application version uninstall pahse) and the app did not uninstalled properly.

    By going to Settings->Application Manager, select you up and just uninstall it. Then i was able to deploy again.

    And even in case that error still persist then browse your phone memory from My Computer go to .Android->.data and if you may find a "myPackage" folder, then delete it. Remember before delete any directory make a backup.

    Good luck

    Tuesday, August 23, 2016 9:12 AM
  • User251611 posted

    @TomOpgenorth said: I'll see this type of error when I'm developing on my device. Then I go to install a release version via TestFlight or adb and this message happens. A lot of the time this happens because your debug version is signed with a different key than the release version. Android detects this and gets angry.

    You get rid of it by uninstalling the older version of your application. YOu might have to go into Settings...Apps, and scroll down to your application and then delete it from there. Once you've deleted your application it should install normally.

    Then when you

    This answer saved my day :)

    Tuesday, September 6, 2016 7:33 PM
  • User242446 posted

    @MikeScott8 said:

    @AmjadAzizi10 said: Ok Guys

    This is a very STUPID error and time wasting!!

    I tried all most everything to delete it from my LG G3. But this helped:

    Run the following command from the Android console: "adb uninstall com.theircompany.packagename"

    This should allow you to uninstall the app manually from the device without having to do a factory reset.

    what if it says DELETEFAILINTERNAL_ERROR

    Thursday, September 15, 2016 6:38 AM
  • User259748 posted

    @merbs said:

    @MikeScott8 said:

    @AmjadAzizi10 said: Ok Guys

    This is a very STUPID error and time wasting!!

    I tried all most everything to delete it from my LG G3. But this helped:

    Run the following command from the Android console: "adb uninstall com.theircompany.packagename"

    This should allow you to uninstall the app manually from the device without having to do a factory reset.

    what if it says DELETEFAILINTERNAL_ERROR

    This is what I'm getting right now

    This is my first few days using Vs with Xamarin - it's been non stop issues and problems

    Load of cobblers

    Friday, September 23, 2016 3:02 PM
  • User127707 posted

    This is an android issue. You have to make sure the app is complete uninstalled from the android device.

    on the device If you go settings -> applications -> find yours and delete it then try again it should work.

    I think it has to do with a signed copy being installed (or not fully uninstalled) then trying to installed a debug version over

    Thursday, September 29, 2016 6:25 PM
  • User267721 posted

    @TomOpgenorth said: I'll see this type of error when I'm developing on my device. Then I go to install a release version via TestFlight or adb and this message happens. A lot of the time this happens because your debug version is signed with a different key than the release version. Android detects this and gets angry.

    You get rid of it by uninstalling the older version of your application. YOu might have to go into Settings...Apps, and scroll down to your application and then delete it from there. Once you've deleted your application it should install normally.

    Then when you

    Really thanks @TomOpgenorth you solved my problem: I deleted "the rest" of the app in Settings...Apps. I said "the rest" because I already unistalled my app via Unistall procedure (drag&drop) but something remained there. Thanks.

    Friday, October 21, 2016 2:17 PM
  • User264925 posted

    @MehulTheXammer said: An alternate solution is to run the command i.e. adb uninstall com.theircompany.packagename from android command prompt located at below path: "AppData\Local\Android\android-sdk\build-tools"

    This worked for me except: 1) I found adb.exe on C:\Users\USER_NAME\AppData\Local\Xamarin\Universal\AndroidSDK\platform-tools 2) After that I restarted my laptop and my tablet (just to make sure).

    Tuesday, October 25, 2016 1:49 PM
  • User145519 posted

    I had a HD failure so had to go to set up a new pc, with a new install of VS2015 and now I'm struggling with this. I've uninstalled the app via Application manager, checked that there are no directories in Android/data, tried adb uninstall (which failed to delete anything) rebooted and I still can't get my app to deploy.

    I'm trying to get the last updates tested before go live (so everything is currently in debug mode) so I'm up against the clock.

    Anyone have any ideas?

    Thursday, November 17, 2016 11:45 PM
  • User145519 posted

    This is occurring on all 5 Samsung Galaxy tab devices. I've spent the lat 2 hrs trying to get it to work, and finally decided to do a factory reset on one of the devices. That did work, but it's not a viable solution when I deploy these tablets into production. I'd appreciate it if someone has any ideas, I'm going to need a resolution before I go live otherwise it'll make the app un maintainable.

    Thanks Steve

    Friday, November 18, 2016 5:39 PM
  • User54654 posted

    try force removing it using adb. adb uninstall {PACKAGE NAME}

    Thursday, December 15, 2016 12:33 PM
  • User287029 posted

    ?????????,??!

    Friday, December 30, 2016 12:42 AM
  • User249511 posted

    @softlion Man, you saved my life. Thanks a lot :smiley:

    Friday, January 13, 2017 9:17 PM
  • User231095 posted

    As mentioned by @MehulTheXammer , if none of the options mentioned above by others works, use adb command prompt to uninstall the package. > adb uninstall xyz.package.name

    This will solve the issue.

    Wednesday, January 18, 2017 5:21 AM
  • User232681 posted

    I was having this problem with VS Android Emulator ,Removing the old Mono Runtime from the emulator solved it for me. settings->apps->uninstall

    Wednesday, January 18, 2017 6:57 AM
  • User42522 posted

    My story:

    I got this error on a device that had no issues earlier. Once I got to this thread tried the following:

    1. I don't have my app's icon in the apps list.
    2. So I checked it in Settings -> General -> Apps and it is not there also, either the app name or the package name.
    3. Then I checked in the File Manager -> Android -> data -> my_package_name. Yes the folder is there but it contained no files. So deleted it.
    4. But all this was not useful.
    5. Then run the command **adb uninstall my_package_name**. But it was giving the error of multiple devices present.
    6. adb devices was listing my phone and another emulator (I swear it was not running).
    7. Then googled and got this [StackOverflow thread](http://stackoverflow.com/questions/14654718/how-to-use-adb-shell-when-multiple-devices-are-connected-fails-with-error-mor "StackOverflow thread") from which I got the clue.
    8. First I ran the command **adb -d uninstall my_package_name**.
    9. Then deployed my app to the phone without any issues.
    Thursday, January 19, 2017 4:36 PM
  • User295290 posted

    Do factory reset and then try. i renamed package name then it is working fine, with old name not working. strange

    Saturday, January 28, 2017 4:19 PM
  • User139544 posted

    @AbhayShiravanthe said: As mentioned by @MehulTheXammer , if none of the options mentioned above by others works, use adb command prompt to uninstall the package. > adb uninstall xyz.package.name

    This will solve the issue.

    Perfect solution ;)

    Tuesday, March 28, 2017 9:59 AM
  • User78191 posted

    @MehulTheXammer said: An alternate solution is to run the command i.e. adb uninstall com.theircompany.packagename from android command prompt located at below path: "AppData\Local\Android\android-sdk\build-tools"

    That one helped me. I appreciate your comment...

    Saturday, April 1, 2017 5:31 PM
  • User311778 posted

    For me the error was inside the Project Options.

    I set Support Architectures,

    armeabi; armeabi-v7a; x86; x86_64

    Friday, August 25, 2017 12:34 PM
  • User311778 posted

    For me the error was inside the Project Options.

    I set Support Architectures,

    armeabi; armeabi-v7a; x86; x86_64

    Friday, August 25, 2017 12:34 PM
  • User285957 posted

    @softlion said: Delete your existing app. It will not be listed under applications with the display name nor have a launch icon. You will find it under Applications with its package name instead. It always is there. Uninstall the package and deploy your new version normally.

    This is a very old "limitation".

    Thanks

    Tuesday, May 22, 2018 8:39 AM
  • User388581 posted

    I found the solution finally.

    adb uninstall com.company.apppackage

    You have to uninstall your old version of APK from your android device by using above command.

    Thanks!

    Friday, January 3, 2020 5:42 AM