I have a UWP app. I'm using Visual Studio 2017 15.4.1. The UWP app is a store app and has been deployed to the Microsoft Store. My app was working fine in the store, and it was also working fine when I hit play in Visual Studio. Then recently, an isolated storage issue started occurring so I went in to the app in "Apps & Features" and hit Advanced Options -> Reset. Somehow this has fried my app installation on my machine. Our app no longer shows up as an installed app, and when I try to install the app from the store, I get an error with a code of 0x80073CF9. So, I can't uninstall, or reinstall on my machine. I've tried running sfc /scannow etc. to find out what's wrong, but nothing seems to help.
This wouldn't even worry me too much, but I can't even develop right now because when I try to run the app from Visual Studio, I get this error:
In order to debug this project, you must consume it from a Windows
Store app project that creates a package and is marked as the Startup
Project
I'm getting this error in the output window from the build
4>DEP0700: Registration of the app failed. [0x80073CF9] Another user
has already installed an unpackaged version of this app. The current
user cannot replace this with a packaged version. The conflicting
package is [APP NAME] and it was published
by CN=[Publisher].
What did I do wrong?
You can use Get-appxpackage -allusers *<appname>* | Remove-AppxPackage
The allusers option is important here.
You can also try to manually remove the content of the application cache folder in C:\Users\\AppData\Local\Packages\. If you have one locked file here, the whole deployment will fail.
I have followed all the instructions to publish my application via ClickOnce
it keeps popping up the above error when I try to install on the host computer
You mentioned that you are using ClickOnce but I see the error is related to a file with extension (.msi), it seems that you have tried other ways to publish your application and one of that you tried is Installer Package (.msi), which should not be related to ClickOnce.
Try to put Only your Original application in a different folder and follow the steps to publish it via ClickOnce. I want you to do this because it seems to me that the error is not be related to ClickOnce nor an error related to the main application.
Wish my answer is clear if not just let me know, good luck
I'm having problems launching an application with VS2017 on Windows 10. Starting in Debug mode, a popup apperars with the message:
Error while trying to run project: Unable to start program ''.
The request is not supported.
If I launch without debug, it runs. If I run it and then attach to the process, it attaches. If I run with administrative privileges, then it debugs (but I can't develop with administrative privileges). I'm owner of the folder where is source code and where project is built.
It works like a charm on previous PC with Windows 7.
Any idea?
You need to check "Use Managed Compatibility Mode" in Tools|Options|Debugging|General.
In the end, i found the solution. The problem is ConEmu set in "Aggressive mode" and as default terminal: it capture my application execution and do some unknown interference.
I removed that setting, and my app work like a charm.
I discovered this issue in Visual Studio 2017, and I found that excluding my code folders from my virus scanner (MalwareBytes) solved the problem in my case.
In my case this was the result of my virus software quarantining the executable as "Malware" because I had used a component in it that connected to the internet. Once I listed my project folder as excluded from malware detection everything ran just fine.
I've developed an simple and small Universal Windows App that uses EF7 and SQLite. The app builds normally and it runs perfectly from Visual Studio. I also can run it directly from Windows 10 in the start menu after the I side loaded it (once the app package is generated).
My problem is that I can't test the app after it's package is generated because of an error on appcert.exe.
If I generate app package to x86 when launching windows app certification from visual studio right after the package is generated I get the error "the appxbundle could not be implanted" even before the test starts.
If I generate app package to x64 when launching windows app certification from visual studio right after the package is generated the test starts normally but before it's done I get the following error: "an unhandled microsoft .netframework exception occurred in appcertui.exe".
The appcert.exe crashes and does not tell me why.
I've searched in google and I've looked at windows log event but found nothing helpful.
I just don't know what to do. My app is finished, I can generate it´s package but I can´t generate the ".appxupload" because of this error I mentioned.
Can someone help me?
The file C:\Program Files (x86)\Windows Kits\10\App Certification Kit\binaryinfo.dll is CLSID {3866CD68-0FC3-4563-8888-E107295BC485} on my machine.
I was able to reproduce your crash by unregistering binaryinfo.dll on my machine and clicking "Validate Store App".
Maybe a fix for your issue to do register this dll (maybe all of them?).
From an administrator/elevated command prompt
regsvr32 "C:\Program Files (x86)\Windows Kits\10\App Certification Kit\binaryinfo.dll"
How your machine got into this state...unknown.
I've made a fresh install of Windows 10 and its SDK in a virtual machine on Virtual Box. The appcertui.exe is running fine and my app was tested successfully.
It might be a problem in the installation of the .NET Framework since I updated from Windows 7 to Windows 10.
I will try to completely reinstall both .NET Framework and the SDK to solve this issue. If none of this works I will reinstall Windows 10 from scratch on my computer.
I was working on an Android project using Xamarin in Visual Studio 2012. I recently upgraded from an HDD to a SSD so I reinstalled Windows and all of my programs.
After cloning my git repository and trying to run the application on my device, I have not been able to get it to run. I was able to start a new hello world project and I got that to run, but I can't get this project to run.
This is what the error says:
The application could not be started. Ensure that the application has been installed to the target device and has a launchable activity (MainLauncher = true).
Additionally, check Build->Configuration Manager to ensure this project is set to Deploy for this configuration.
I have searched for a solution to this issue but have been unable to find anything that worked.
I solved the issue. Somehow the application still existed on my device even though it did not show up in my applications and I needed to remove it.
The solution was to find an old APK that I had emailed and I installed that. Then I uninstalled the application and deployed it again from Visual Studio. This time it worked.
You can read more here: https://forums.xamarin.com/discussion/8501/install-failed-update-incompatible
EDIT (March 13th, 2017):
Seems a lot of people found this answer useful so I decided I should update it with an alternate method to uninstall the app if you don't have access to an old version.
As Atul Chaudhary and Nestel mentioned, you can open up your adb command prompt and run adb uninstall <com.your.application.package.name>. If there are any remnants of your application which remain this should get rid of them.
Renamed Application name.
Added Package name.
App. started working on Emulator, Renamed application again, app. continued to run.
Note: Resetting device, un-installing the app. and related runtime etc. from settings did not work for me.
Hope this helps someone.
Running this command from the adb shell solved it for me:
adb shell pm uninstall -k com.packagename
To access the adb shell from Visual Studio Tools -> Android -> Android Adb Command Prompt.
Very interesting error, seems like Visual Studio is unable to unistall the previous version completely.
Obviously the OP figured out the issue to their problem but I still wanted to post an answer relating to an issue I had with the same error message. I am using Visual Studio (within Parallels) and attempting to debug the app on a Xamarin Android Player instance (which is running on my Mac).
I kept getting this error and realized that a different, more helpful, error message was showing up in the Build Output saying that I was not supporting the correct architecture.
Heading into the Android Project Properties -> Android Options -> Advanced -> and checking x86 finally allowed my to successfully deploy to the Xamarin Android Player.
The ADB approach does not worked for me.
I did not want to factory reset my phone nor uninstall my apps so I have managed to deploy by changing the package.
Right click on your Droid project
Select Properties
Got to Application Manifest
Change the Package name
Re-deploy your project
Hope this helps
I had the same error today, trying to run Xamarin Android-app on Xamarin Android Player. To fix it I needed to check the "x86" box at the "Supported architectures" section. So you might want check this section.
I experienced this problem when there was not sufficient memory on device. After "successful" deployment the app was missing even from the app list in Settings. Deleting through adb gave me Failure which indicated it was not installed. In Output log in VS2015 I was having the same message as OP. Finally it worked after I cleaned up about 50-100 MB, even though in App Settings it showed me that there were 500 MB free. I tried different solutions (deleting through adb, cleaning, building then deploying) but only cleaning up worked.
adb uninstall did the trick. The strange thing is that even if you run the command to list all app that are installed it will not show up but if you run the uninstall command with ur package name which should be ur project name or name that you have assigned you will get the success result which means it got uninstalled and to check that if run the uninstall command again with same package name u will get failure command. Then deploying ur package again should work
In my case issue was two activities were Launcher activities,so I made one of them Launcher activity.
You can remove
<intent-filter>
<action android:name="android.intent.action.MAIN" />
<category android:name="android.intent.category.LAUNCHER" />
</intent-filter> from AndroidManifest.xml file or
MainLauncher = true from .cs Activity file attribute
If you've reinstalled everything you may have to set the configuration manager back up in VS.
In Visual Studio: Build -> Configuration Manager -> Put a check in the "Deploy" box.
I've managed to solve it by wiping user data from emulator.
From AVD Manager, when you start the emulator, check "Wipe user data" and your emulated device will behave like new.
Problem itself appeared after updating to Android SDK Tools 25.1.3.
I could not get this working, initially. Tried removing everything (Mono runtime, app, etc.), but to no avail.
What did work was renaming my package, which was fine in my case since I haven't release my apk yet. Some ghost version is obviously still stored on my unit.
Renaming Application Name and Package Name (go to Manifest settings) where helped to resolve this issue
The only alternatives which help me solve this were the following:
From the Xamarin Android Studio home page (where all devices are displayed), click on the "three-dots" button and then Factory Reset.
OR
Install a new device and deploy your app there.
Whenever I encounter this problem, I publish the app and install in manually using
adb install "<path to apk file>"
in the Android Adb Command Prompt.
Hopefully, a fix is out soon, according to
https://github.com/xamarin/xamarin-android/issues/3727
Happened to me today, after updating a project from Git and running in Android Emulator. Uninstalling the app from emulator, performing Clean and Rebuild in VS and instaling the application again helped.