I am able to sync and manage music, pictures, etc on my samsung focus using my boot camp installation on my macbook just fine but when I try to deploy a test application to my device, I get "This operation returned because the timeout period expired" via VS2010. I get the same thing when I try to manually deploy the application using the application deployment utility.
I am able to do this fine from my dell desktop. Anyone else experienced something similar to this? Any thoughts on why this is happening?
FYI - I get the same behavior whether I am booted into boot camp or using VMWare fusion and USB pass-through.
From this thread:
Try disabling the WiFi connection on your phone and deploy. If that doesn't work, try disconnecting the device and closing Visual Studio and Zune. Then reconnect the device and reopen Visual Studio.
Related
I have some old windows 10 mobile phones, that I want to give a second life as a music device for my kids. Since I have Visual Studio 2019 Enterprise at my hands, I thought I try to create something myself.
Not I tried to create an UWP app and a Xamarin app and try to debug them on the phone (connected via USB, developer mode enabled, unlocked). But with both I get this error:
DEP6957: Failed to connect to device '127.0.0.1' using Universal
Authentication. Please verify the correct remote authentication mode
is specified in the project debug settings. COMException ... HRESULT:
0x8007274D) [0x8007274D]
The apps are still in their initial state after creating the project, no modifications done. The settings for debugging are set to: Debug, ARM, Device
I had some experience with an older Visual Studio version and windows phone 7, back then it just worked and all the documents I could google up suggest, while there are new ways, it should still work via USB.
If you plan to develop Windows 10 Mobile App, you need to use Visual Studio 2017 and make sure the target version of the app is below 14393.
Visual Studio 2019 no longer supports deploying UWP apps on mobile phones.
Best regards.
sometime i must reboot service something like windowsphone ipoverusb
I'm developing a UWP app for Windows 10 Phone. Since some days when I try to deploy the app from within Visual Studio I get asked for a PIN in order to connect to the device
In the phone settings I can trigger pairing so a new PIN is generated for me. But when I enter that PIN, a new dialog appears telling that the PIN was wrong:
If I press 'Cancel' then the deployment is interrupted with an error message:
1>Error : DEP6100 : The following unexpected error occurred during bootstrapping stage 'Connecting to the device '30F105C9-681E-420b-A277-7C086EAD8A4E'.':
It's strange but some days ago I was not asked for the PIN when I deployed the app. :-( So currently the only option I have is deploy via the web portal. This works but it's enormously slow :-(
Can someone tell me how to solve the problem or what PIN should I enter in order to achieve the deployment?
I had this problem today, closing visual studio and restarting IpOverUSB service fixed this issue for me.
You might want to take a look at Ricardo Pieper Question he has listed all the things he tried to do and all the things that might work.
It looks like the problem was caused by the fact that I'm developing inside a virtual machine (VMWare Fusion on Mac). After setting up the development ebvironment on a PC the deployment works fine.
I can even debug the app running on the phone from inside Visual Studio.
Here's a solution which worked for me:
I had the same problem on my Macbook running VMWare Fusion and trying to debug on my Lumia 950 phone. I was nearly giving up, then I tried using the free VirtualBox and with a virtual USB 3.0 port (which requires the VB extension pack). And it worked!!
Here's my setup:
VirtualBox 5.0.14
VB Extension Pack
Win 10 Development VM from Microsoft – the VirtualBox variant, Build 201601: https://dev.windows.com/en-us/downloads/virtual-machines
Lumia 950 with Windows 10 Mobile 10.0.10586.29
In the VM, I configured to use the USB 3.0 port, since with USB 1.x the phone device driver could not be installed by Windows 10.
The VM contains Visual Studio 2015; I created a UWP JavaScript application and ran it with "Debug" on the connected Lumia device.
Had to go to the Developer options on the device.
Switch back to "Windows Store Apps" option, and then back to "Developer Mode"
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.
I have solved it with the following steps:
Open Windows Search, search for "services".
Find the Service “Windows IP over USB Transport (IpOverUsbSvc)”.
Alter initialization type for automatic and click mouse right button and select Start.
Try running !
I put this answer on another post but I guess some did not feel it was an appropriate answer because I didn't find the exact cause - Can't deploy window phone apps to Emulator. Error DEP6100 & 6200. I see that you are having a few issues that I did not originally have but overall I was having weird symptoms. Below is what I did to remedy the DEP6100 and DEP 6200 errors.
I'll start by saying that reloading Visual Studio 2013 and Windows Phone SDK 8.0 did not fix my issue. What did correct my issue was creating a blank project within the Visual Studio Express 2012 for Windows Phone and deploying the project. Then I went into Visual Studio 2013 and tried deploying my project again and voila, it worked. Why, I have no idea but my guess is there is a file or configuration that is set up by VS Express 2012 for WP that has been missed in the VS 2013 with built in WP SDK.
I had a similar experience with VS 2013 where I could not connect the debugger to the device AND the app would crash out with WIFI enabled (emulator was fine)
I solved these problems by installing VS2015 Enterprise RC
I am facing a strange issue with Windows Phone Emulators for last a few days. When I try to run any windows phone application from Visual Studio 2013/2012, it initially starts the emulator and then stops with an error displayed in the error window inside visual studio:
Error : DEP6100 : The following unexpected error occurred during boostrapping stage 'Connecting to the device':
SmartDeviceException - App deployment failed. Please try again.
I have been trying many solutions in order to fix this issue but nothing helped. At last I re-installed the whole windows 8.1 and then visual studio 2013. Then I created a windows phone 8 application and run it smoothly in windows phone emulator.
Then I installed all windows updates including windows 8.1 update 1. After that I installed the visual studio 2013 update 2. Now if I run any new/existing windows phone 8/8.1 project I get the same error again. Seems like there is something wrong with windows 8.1 updates or visual studio 2013 update 2.
Any help?
Open network and sharing center
Change adapter settings
Check if vEthernet [Windows phone emulator internal switch is enabled)
Try deploying it to the emulator now
If above does not work
Delete the virtual switch(s) if any and do a deployment
If it still does not work, connect to the internet via a LAN
Keep you’r wifi on
do a deployment to the emulator
Most cases above method worked !
I had the same error when i tried switching the target OS version of my app from Windows Phone 8 to 8.1. With 8.1 you get a new manifest file and if, for app or publisher identification string, you have different values in one manifest file than in the other, it will output that exact error when trying to start the app in the emulator. However after searching the web back when i had that error, this error seems to have quite a bunch of possible sources, this being only one among many other, but be sure to check it.
Uninstalling the symantec antivirus fixed my issue.
I'm trying to debug an app running inside the windows phone 7 emulator, but I can't connect to it from visual studio - Attach to Process -> selecting Windows Phone 7 Emulator transport displays an error:
"Unable to connect to 'Windows Phone 7 Emulator'. Not implemented"
What am I missing?
As a workaround:
open the solution configuration manager
next to build is a deploy column, uncheck your project
press F5
This will launch the app that is already on the device without overwriting it (and deleting its storage).
I don't think it's possible to connect to an app that is already running on the emulator.
It sounds like you're trying to connect to the emulator directly yourself,rather than the app running in it. Which I don't think is what you want anyway.
It may help if you think of the emulator as a virtual machine. That's what it is. (near enough.)
If you want to debug an app in the emulator, you need to launch it through Visual Studio.