Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Windows Phone 8.1 Device (Lumia 930) and VS2013 debugging works only with disabled WiFi

There were errors in VS2013 when a Windows Phone 8.1 App is launching for deploy and debug:

Error 1 Error : DEP6100 : The following unexpected error occurred during boostrapping stage 'Connecting to the device': SmartDeviceException - Deployment failed because no Windows Phone was detected. Make sure a phone is connected and powered on. AppWP

Error 2 Error : DEP6200 : Boostrapping 'Device' failed. Device cannot be found. Deployment failed because no Windows Phone was detected. Make sure a phone is connected and powered on. AppWP

After performing of many method trying to eliminate this problem (disabling firewall, reinstalling SDKs, updating Lumia 930 to the latest Windows Phone developer preview), I managed to deploy and run an app with debugging. And as topic says, deploying and debugging is possible only with disabled WiFi on the Phone.

After enabling WiFi on the Lumia 930 device while connection of VS-debugger/PowerTools is established, then the debugging session stays connected and working. But if I disconnect Windows Phone Developer Power Tools (8.1) and try to connect again (while WiFi is enabled), it says:

Power Tools can't communicate with the device. Here's the error message:

0x80131600 - 0x80131500 - 0xC0000374

Visual Studio can deploy and start a new debug session after enabling of WiFi even after restarting of a VS2013.

But, after restarting the Windows Phone IP over USB Transport (IpOverUsbSvc) service, VS2013 becomes unable to deploy and debug again until WiFi is disabled again.

That's how it behaves.

UPDATE: After updating to Lumia Denim, the bug was fixed.

like image 260
Lessneek Avatar asked Jan 03 '15 09:01

Lessneek


1 Answers

I have solved it with the following steps:

  1. Open Windows Search, search for "services".

  2. Find the Service “Windows IP over USB Transport (IpOverUsbSvc)”.

  3. Alter initialization type for automatic and click mouse right button and select Start.

  4. Try running !

like image 94
Erick Wendel Avatar answered Oct 18 '22 21:10

Erick Wendel