I've been working in a Unity app with Hololens emulator in Visual Studio 2017 in Windows Pro, and it was working great until last night where I started to get the following issue every time that I try to deploy my application into the Hololens emulator:
Error DEP6957 : Failed to connect to device '[device_ip]' using Universal Authentication. Please verify the correct remote authentication mode is specified in the project debug settings.
I've tried to do the following things without success:
Clean/rebuild solution
Checked 'uninstall/install' checkbox in the UWP project settings
Deleted Hololens virtual machine
Uncheck/check Hyper-v feature (and restart PC after each try)
Restarted computer
No luck. Sometimes, I am able to make it work, but after 30 seconds to 1 minute, the hololens emulator gets frozen and then it closes itself; again, this was working fine until last night, and I have not installed anything different, unless an automatic windows update did something. This happens with all the applications, and they run just fine in the Unity player.
I would appreciate your help on this, I just don't think the only solution is to uninstall/install Visual studio and all its components, it makes no sense, since everything was ok.
Thank you.
UPDATE
I've just noticed that if I connect the laptop to the internet by using an ethernet cable, it works, it only fails in WIFI, have you seen that before? I also have another UWP that I deploy remotely to a raspberry and it also works only with ethernet, but both of them were used to work in wifi? any idea?
Related
My setup
HoloLens
Windows 10 October 2018 Update (10.0.17763.134)
Desktop
Windows 10 Enterprise
Visual Studio Community 2017 Version
Unity 2018.2.19f1 (Latest 7th December 2018 Update)
The Problem
I am unable to deploy any application to the HoloLens, but able to deploy it on hololens-emulator. I'm attempting with the Origami application exported from Unity as in the tutorial. I'm able to pair with the HoloLens easily and I have developer mode on. Visual Studio also does auto-detect the device as a remote machine. But when I attempt to deploy it, I always get the same "DEP0100" error, that the device is not in developer mode though the device is already in a developer mode. I'm at a loss for what else to try, or what setting I've missed. I've reset the HoloLens several times and reinstalled Visual Studio only to get the same thing.
I have already tried the solution mentioned here Unable to deploy HoloLens application but it didn't work for me.
It is not clear what you got. But I have couple ideas:
You connected to HL as Remote Machine, but HL is Device.
You built an appx as x64, but HL is x86.
You didn't install a proper runtime, debug or release.
You use older SDK than HL platform version.
You minimal target platform is higher then HL platform version.
Maybe something else. You need to investigate the Hololens logs. Open "Windows Device Portal"/System/Logging.
Then you need to select some providers with severity by choosing them in box and clicking "Enable". I usually begin from "Microsoft-Windows-WinRT-Error" ETW provider.
DO NOT CLOSE THE LOGGING PAGE!!!!!
Start the debugger with app, see the error and go to Logging page. Try to find out the root of issue.
I have seen few posts here about same error but none worked for me.
I am trying to deploy UWP from VS2017 from one machine to a Surface machine that is USB connected to the machine running VS2017.
Both machines are running Windows 10 Pro, 17134 (1803) April Update.
Surface machine has enabled Developer Mode in "For Developers" settings and Developer Mode package is installed on it and Remote tooling for desktop is enabled. It is also USB connected to the machine running VS2017 Enterprise 15.7.5
According to MS documentation, that is all what is needed to deploy to device. However, deploy fails with error
Severity Code Description Project File Line Suppression State
Error DEP6200: Bootstrapping failed. Device cannot be found. SmartDeviceException - Deployment failed because no device was detected. Make sure a device is connected and powered on. [0x80131500] MyApp.App.UWP
I was unable to deploy either to device or to use remote debugging.
Deploying to device was failing with the same error message as above. Interestingly, even if device (Surface in this case) is not USB connected to my dev machine at all, I get same error which basically makes sense. But I dont know why I get that same error when I connect Surface tablet to my dev machine.
Deploying for remote debugging did not work since my Surface tablet is not connected to same LAN as my dev machine.
So, for my testing purposes, I deployed by using USB stick
Right click on UWP project, choose Store, then choose Create App
Packages ....
In Create App Packages window, select "I want to create packages for
sideloading"
Click Create
Leave Local Machine as target device for validation
click on Launch Windows App Certification Kit button to launch it
and go through steps until complete
Once package is completed, I copied entire folder onto a flash drive
and moved the content of the folder to my Surface tablet
Then on Surface tablet, right click on the Add-AppDevPackage.ps1
file and choose Run This PowerShell
this will start deployment and deploy the app
I've read every StackOverflow that I could find on this issue, but I still can't work it out.
I'm trying to deploy an app to actual device (NOT emulator). But I receive the following error when i try to build:
Severity Code Description Project File Line
Error Error : DEP6100 : The following unexpected error occurred during bootstrapping stage 'Connecting to the device '30F105C9-681E-420b-A277-7C086EAD8A4E'.':
SEHException - External component has thrown an exception. App1
and
Severity Code Description Project File Line
Error Error : DEP6200 : Bootstrapping 'Device' failed. Device cannot be found. App1
It's worth mentioning that I went from Windows 7 to Windows 10. It's also worth mentioning that my computer was missing the IpOverUsbSvc.exe (not just the registry post, but the actual service was missing). Couldn't find any way to get this back so, so my colleague sent over the .exe and the DLLs and I placed it in it's location. And the service is now running and no longer gives any errors. My device is recognized by the PC, it's running Windows 10 Mobile (but I've also tried with a device running Windows 8.1).
Specs on PC:
Windows 10 Pro (Build 10240)
Using Visual Studio 2015
UWP Tools
Any suggestions to fix my nightmare? Thanks!
Steps that helped me. I have windows 10 mobile build 10581 (and now 10586) installed on phone
Turn off Developer mode on your phone.
Deploy app (UWP or SL) by VS2015 -> Error.
Turn on Developer mode on your phone.
Deploy app (UWP or SL) by VS2015 -> Working.
If you change another device or re-connect you must close VS2015, re-launch and do again!
Finally managed to find a solution to this illusive bug.
It seems that if I didn't have the Windows Phone 8.1 Tools installed I couldn't build to an ARM device (not even Windows 10 Mobile).
So my step to solve this was:
Go to Control Panel -> Programs and Features -> Microsoft Visual Studio ... 2015 -> Modify. And then select the Windows Phone 8.1 Tools.
Pretty pissed that one can't get a reasonable error message when things like this is missing.
I had this issue after updating my device to win10 ver:10.0.10581.0. I tried many things but finally after installing latest sdk and emulators i got it working. You may try installing from this page sdk and emulator:
https://dev.windows.com/en-us/downloads/windows-10-developer-preview
Somehow the new emulators were not visible in vs, they got visible after few restarts and then on device debugging started to work.
But one problem still remain from me that vs crashes after ending debug session with device.
desktop-->my computer--> right click--> management--> service--> start the service Windows Phone IP over USB Transport (IpOverUsbSvc) although maybe the starttype is set as automatic
Seems like there are many issues causing the same error message.
This one worked for me Windows Phone deploy Issue
Essentially you need to remove/uninstall the device from Windows. Then after unplugging and plugging back in, the device and drivers are reinstalled.
I tried many of the suggested solutions to no avail.
After changing the USB-C cable from a USB 3.1 port to a USB 2.0 port on my computer, the error goes away. YMMV
I see it is quite an old post...but I still get this problem. In my case, this happened after I deployed to a second phone I had for testing. After that, VS 2017 now only wants to deploy to that phone and not to the other phone no more. If I start another project, the other phone is recognized and deployable to (listed as device under debug).
Restarting system fixes this...
Also, if I add another project as reference (like a background task) to my project, I will loose the ability to select the devices and emulators under debug. VS 2017 simply then seems to deploy to the last device selected...(really no clue what this is). I have not been able to get the selection of emulators and devices back yet on this one. I only will have the "Start" and "Download new emulators" options. I think this has to do with the fact that VS maybe doesn't know the type (like arm/86/64) of the reference project because it is not set (not needed as this defies the purpose of referencing a project for dynamic references and not the compiled device specific file...)
Hope it helps someone ....
I uninstalled the existing version of the app in device and re-ran it and it worked for me
I got that error for a really simple reason...just opened a new solution I downloaded from GitHub, pressed F5, and got it!
I had left my build configuration in the default "Debug - ARM" setting, when I changed to "Debug - x64" it worked fine!
(Just adding another reason for completeness, not likely to affect your case!)
In case it's helpful for others... I got: DEP6701 bootstrapping failed ... access denied.
Thanks to comments here, I only dev-locked then dev-unlocked my phone (was originally dev-unlocked). Totally works now (took some time installing missing frameworks at first). All good.
Thanks
One more thing could be tried.
Uninstall the existing app if any and then deploy from Visual Studio.
Try on another usb port. It worked
I'm trying to deploy my first Windows Phone 8 app to my brand new Lumia 920, after getting everything up and running on the emulator, but I'm running into the following error during deployment:
1>------ Deploy started: Project: AudioFilteringPhone, Configuration: Debug ARM ------
1>Deploying C:\Users\<username>\Documents\Visual Studio 2012\Projects\AudioFiltering\AudioFiltering\Bin\ARM\Debug\AudioFiltering_Debug_ARM.xap...
1>Connecting to Device...
1>Optimizing for device...
1>Installing the application...
1>Deployment of application to device failed.
1>Error writing file '%FOLDERID_SharedData%\PhoneTools\11.0\Install\{29b31259-9af9-47a5-9891-c3098315d3d8}\AudioFiltering_Debug_ARM.xap'. Error 0x80070003: The system cannot find the path specified.
If I manually try to deploy using the Deployment tool, I get the same error. Does anyone know what the cause of this is and how to alleviate it? This happens even if I just start a new WP8 app and immediately try to deploy it, so it's something wrong with my environment, not my application configuration.
I had exactly the same problem, but solved it by simply rebooting the phone. No software updates were required.
It turns out that there were software updates that needed to be installed. If anyone knows a way to find out the names of the updates applied, I will post them here, otherwise all I can say is that I had to update to OS version 8.0.10211.204.
This also can be because of wrong USB cable or port. I have a long cable for charging which works with android devices, but doesn't with WP.
Or maybe using another USB port helped.
I am new to both the android and android development so I'm not on familiar ground here.
When I start the emulator I have no service. Therefore I have no internet connection on the emulator.
I am running Windows 7 and I generally run the emulator via eclipse.
My host machine is connected to the internet via the Local Area Network. There is no proxy.
I have tried:
Disabling all network adapters except for the Local Area Network [link]
Running the emulator from cmd line with: emulator -avd -dns-server 8.8.8.8
Reinstalling the SDK Tools 9 and Platform Tools (rev 2).
Restarting the machine! :P
Is there a setup needed to specify to simulate a 3G connection? Or could this be a Windows 7 permissions issue? Or am I doomed like these folks: link link
Ah! found the solution.. I uninstalled the entire SDK and reinstalled it to C:/Android. I deleted the C:/Users/[your-name]/.android folder and recreated an avd. Voila.. Something in there worked!
[edit]
Actually it looks like you have to keep restarting the emulator until it connects. I will often get no service so I restart a bunch of times till it works.
I found that 'Airplane Mode' was enabled by default in the standalone android emulator - this may also be the cause in the sdk version. Turning this off (by holding down the red power button until the menu came up, and then toggling the airplane mode button/section) allowed the emulator to 'find service' and connect properly through the LAN.