I am developing a Universal Windows 10 app and I get an annoying problem every time I try to run project after I uninstall the app from windows start menu. The scenario is:
I run project on local machine - app is running good;
I press Shift+F5 to stop runing;
Go to Windows start menu and uninstall just installed app;
Run app again from Visual Studio;
Get error 1>Error : DEP0700 : Registration of the app failed. An internal error occurred with error 0x80073D05. See http://go.microsoft.com/fwlink/?LinkId=235160 for help diagnosing app deployment issues. (0x80073cf6)
NOTE: sometimes Clean Solution + Rebuild Solution helps, but sometimes only system restart solves the problem. Is this an official bug or I am missing something?
I was facing the similar problem, and as per this link
https://social.msdn.microsoft.com/Forums/en-US/566e53ec-2020-4969-9f17-f0a5a916f027/error-dep0700-registration-of-the-app-failed?forum=winappswithcsharp
we need to locate the app`s package in C:\Users\UserName\AppData\Local\Packages and delete it. This error occurs when after installing if the system is not able to delete the complete package from Local.
This is not the official bug in this case.
Please check if your project is build before and then deployed (please see screenshots below) and let me know whether problem remains and what is the version of the Windows platfrom you use.
You can check it using search window and type "winver":
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.
When I develop for Windows Phone, I am able to side load the current version of the app (version on the Windows Store) and then run the app in development in the same emulator. This give me an idea if the app update work.
I am trying to do the same thing with Windows 8 App but it doesn't work. I side load the current version of the app and then run the app in development and I get the following message: "The app ... is already installed on this machine".
How can I test the update path for my Windows 8 app?
Thanks!
When you build an app from the Windows Store it gets packed up into a an .appx file, which, you can submit for certification or side load using the PowerShell script.
When you run it in a development environment (pressing “play” in Visual Studio) it installs an unpackaged version in a different directory. What this means is that you must remove the packaged version before you can install the unpackaged one.
However, you can build a package and side load that one, as long as the version number is larger than the one already installed:
In Visual Studio, right click on your project and select “Store” and then "Create App packages...". When asked if you need to build the package for upload to the Windows Store, select "No".
Choose an output location and enter a version number higher than the one of the currently installed version
Wait for the project to build.
Start Windows PowerShell from the start screen, and navigate to the output directory from the above step
Navigate to the sub directory for the correct build of your app (eg. “MyApp_1.0.1_x64_Debug”)
Run .\Add-AppDevPackage.ps1 and wait for the app to install.
This will have upgraded your current packaged install to the new version, which will allow you to test that any upgrade code in your app works, you will not, however be able to debug it in Visual Studio.
Note, that when your done testing, you should use the remove-appxpackage <Your app ID> (Documentation) PowerShell command to uninstall the side loaded version to prevent you from having issues if you try and install a version from the Windows Store.
Hope that's helpful.
-Andy.
Update: I forgot to mention, you may have to run Set-ExecutionPolicy RemoteSigned from an admin PowerShell window before you are able to execute .ps1 scripts - http://technet.microsoft.com/en-us/library/hh849812.aspx
There is a weird issue I am facing. I created my first windows service looking through various blogs and tutorials.
Then created setup for that adding installer etc. It works fine while installing , un-installing via Visual Studio but it fails when i deploy it .
Below is a summary of the errors, details of these errors are listed later in the log.
* Activation of C:\Users\bhuvint\Documents\Visual Studio 2010\Projects\CPNS Library\ServicePackage\CommonPushNotificationWindowsService.application resulted in exception. Following failure messages were detected:
+ You cannot start application CommonPushNotificationWindowsService from this location because it is already installed from a different location.
+ You cannot start application CommonPushNotificationWindowsService from location file:///C:/Users/bhuvint/Documents/Visual%20Studio%202010/Projects/CPNS%20Library/ServicePackage/CommonPushNotificationWindowsService.application it is already installed from location file:///C:/inetpub/wwwroot/ServicePackage/CommonPushNotificationWindowsService.application. You can start it from location file:///C:/inetpub/wwwroot/ServicePackage/CommonPushNotificationWindowsService.application or you can uninstall it and reinstall it from location file:///C:/Users/bhuvint/Documents/Visual%20Studio%202010/Projects/CPNS%20Library/ServicePackage/CommonPushNotificationWindowsService.application.
I have already un-installed the service and trying to install it from the deployed service in the same pc to test. But it fails with above error.
I feel i have deployed the windows service the wrong way. Could you guys please suggest how to deploy a windows service ?? (I have looked through net. All suggest building it and installing it from visual studios. But how to publish it is the thing which i need.)
Please help asap.
Possibly you built the setup project before uninstalling the preovious service. In that case you can't use the new setup to uninstall the service, since the setup won't be the same and can't be able to access the service installed.
You should try to go to a previous version of your project and uninstall the service and for the future unistall the service each time you're building your setup project.
This happened to me several times.
Run visual studio in debug mode, and in your properties of your service project goto tab build events in Post-Build event command line and add a -d so you can run your service without installing it, it will run as an console app
The LocalService account acts as a non-privileged user on the local computer, and presents anonymous credentials to any remote server. Use the other accounts with caution, as they run with higher privileges and increase your risk of attacks from malicious code.
If your service application will not install correctly, check to make sure that the ServiceName property for the service class is set to the same value as is shown in the installer for that service. The value must be the same in both instances in order for your service to install correctly.
NoteNote
You can also look at the installation logs to get feedback on the installation process.
You should also check to determine whether you have another service with the same name already installed. Service names must be unique for installation to succeed.
STUPIDITY PERSONIFIED
As i told i was deploying my service. So this published code had a "setup.exe" file to it. Now I had already created a setup project for the windows service , which i was using for the installing , uninstalling . And i din't know (These words needs courage !!) that msi file created is required to install the windows service. So as i got through the folder structure of the setup project. I came across the .msi file . And hence the problem got solved. The Main problem was :
Me not knowing to use setup projects
And I confused setup.exe with the published windows service with the setup of windows service.
I am really sorry for stealing bandwidth off your precious time. Thanks to all for the valuable inputs.