I\'m trying to debug the application via usb on my phone, but the development environment does not see my phone (Chperia Z compact e5823). The driver was updated, the developer mode was enabled, USB debugging is enabled. What could be the problem?
Possible problems:
Android SDK not setup or incorrectly setup
adb not setup or incorrectly setup
Also there are some "packages" you need to (should) install inside the android sdk manager. The Google USB Drivers, for example, is one of them.
Related
I'm trying to deploy a UWP app from my Alienware 18, Laptop with Windows 10, version 1803 to a Tablet Galaxy TabPro S with Windows 10 version 1803 as well.
I had activated developer mode on the device target and the USB device discovery option as well.
First I tried connecting a USB Cable from my laptop to the tablet which has a USB-C port.
But My laptop doesn't even find it.
What I want is to find a way to deploy a UWP from my laptop to the tablet, I made some research and I found out that, only HoloLens and Windows Phone 10, are findable using USB Connection.
So what step should I follow to successfully remote debug my app to a windows 10 Tablet.
I would appreciate details because I tried to follow remote deploying but I haven't been able to successfully find the tablet.
The Windows 10 on your tablet, just like on your development machine, supports remotely debugging over the network rather than over USB. Make sure both machines are in developer mode, with the other machine also having Device Discovery turned on as described here. Both should connect to your WiFi as a private network. After that it should be as simple as configuring your project to deploy to the other machine, rather than locally, as described here and here. Don't forget to pair them with a PIN.
If you host a web API on your development machine, configure your firewall as described here.
Use remote debugging over at https://learn.microsoft.com/en-us/visualstudio/debugger/remote-debugging?view=vs-2017
Make sure you follow the instructions, sometimes remote debugging is barred by firewall so check that.
Alternative right click your main project, go to store then click create packages for sideloading and then send the package over at your Samsung device.
So what step should I follow to successfully remote debug my app to a windows 10 Tablet.
To run a UWP app on a remote machine, you must attach to it using the Remote Tools for Visual Studio.
In some scenarios, the remote tools are automatically installed when you deploy to a remote device. For example,
For Windows 10 PCs running Creators Update and later versions, remote tools will be installed automatically.
Then, your remote device and the Visual Studio computer must be connected over a network or connected directly through a USB or Ethernet cable. Debugging over the internet is not supported.
After that, you need to configure the Visual Studio project for remote debugging. In the properties of the project, select the Debug and choose the Remote Machine from the Target Device list. In general, I will input the remote machine's IP address, you could choose Find to choose the device from the Select Remote Debugger Connection dialog box.
Next step, please move to your Tablet, you need to Set up the remote debugger. You must have administrative permissions on the remote computer. Then, open the Start menu and search for Remote Debugger. If you could find it, just start it normally. If you cannot find it, you need to install it Remote Tools manually. See this link to Download and Install the remote tools. Once the Remote Debugger started, you could do some configurations. After that, you could choose Start Debugging on the Debug menu (Keyboard: F5). The project is recompiled, then deployed to and started on the remote device. Please read Run UWP apps on a remote machine in Visual Studio for more information.
We develop an app which is on the Windows Store and targets Windows 8.1 in it's build. The app is fully submitted to the store and works perfectly on Windows 10 devices. However on all Windows 8.1 devices we are receiving the following message when trying to install the app from the store:
Purchase Error - Sorry, this app can't be installed because your PC might not meet some of the requirements. Go to the app's description page to check for any requirements listed under details.
The apps description page has no requirements other than supported processors of x86, x64, ARM. There is nothing special about the requirements for the app and we are not using anything out of the ordinary.
The app works fine if it is side loaded or remote debugged onto a Windows 8.1 device. It just seems that the Windows Store for whatever reason is incorrectly blocking its download onto any Windows 8.1 devices.
Has anyone any ideas? We have attempted a wsreset.exe without success.
Thanks,
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"
When I go in to debug the app, it asks me to choose where I would like to deploy it. When I select Windows Mobile 6.5.3 Professional Emulator and click the Deploy button, it starts to work and throws up a command line and then it goes away and Visual Studio doesn't appear to be in debug mode.
I have the Device Emulator open, Windows Mobile 6.5.3 Professional Emulator loaded and cradled. Can someone help me figure out why it will not let me debug this project?
Brad, I downloaded the code and just unpacked the zip to D:\boxoffice_mobile (a local drive partition). Then I started VisualStudio 2008 and opened the solution file. I get a warning message that the project is not loaded from a trusted location (http://msdn.microsoft.com/en-us/library/bs2bkwxc%28v=vs.80%29.aspx). As I do not use a network drive, I ignored the warning two times and the projects load all fine.
BTW: I found a great tool to manage these 'security' warnings: http://blog.codingoutloud.com/2010/03/05/the-project-location-is-not-trusted-dealing-with-the-dreaded-unblock/. The message had nothing to do with a remote file access.
Then I just looked at the solution configuration to ensure that only the needed projects are build and did no change, as only BoxOfficeMobile and WebserviceTest are set to build and only BoxOfficeMobile is set to deploy.
Then closed solution configuration manager and just pressed F5 to start debugging to see what happens.
The startup project BoxOfficeMobile was build and deployed to "Windows Mobile 6.5.3 Professional Emulator". The emulator started and the files were deployed and the project was stopped by a breakpoint inside the code:
Here is another screen shot with the emulator set to 'Display: Always on top':
So, as you can see, the project is fine and the debug issue on your site is caused by a different setup.
Do you load the project from a network drive share? Try moving it to a local drive and run it from there.
Did you change Device settings in the VS2008 Tools:Options menu? Here is my setup (as coming as default, I did not change anything):
and the details:
The additional settings available via the buttons are empty (Configure) or unchanged (Emulator Options).
I am very interested in seeing what you changed to be not able to debug the project.
before you start developing for Windows Mobile 6.5 Prof, you need to setup your development environment.
First, install Visual Studio 2008 (no express version)
Download and install either ActiveSync (host OS <= Windows XP) or Windows Mobile Device Center / WMDC (Windows Vista/7)
[optional] Download and install Device Emulator Manager
Then download and install Windows Mobile 6.5 DTK (http://www.microsoft.com/en-us/download/details.aspx?id=5389)
Now, you can start a new C# project inside Visual Studio 2008:
Follow the wizard:
The list of Target Platforms depend on the Mobile/CE SDKs you have installed!
Select either .Net Compact Framework 2.0 or 3.5. The choose depends on what is installed on your PC and what is available on the device. If the device comes with 2.0 pre-installed, I would choose 2.0 except for I need something only available in 3.5 (ie Mobile.Status namespace).
Now you get an empty form:
You can change the target device in the project properties:
If you want to change the target platform, look at "Change Target Platform" in Project menu or just right click the project in solution explorer and select Change Target Platform:
The above has nothing to do with Device Emulator Manager or the installed Emulator Images!
You can run a WM5 targeting project on a Windows Mobile 6.5 device if you want.
To start debugging and SmartDevice application inside an emulator. Just Select an Emulator entry from the target device list in Project properties or just in the SmartDevice toolbar. Then click Debug and "Start Debugging". VS will start an emulator with the specified emulator image and deploys your project application files and start remote devugging.
You may also start an emulator image using DeviceEmulatorManager and then cradle the running Emulator image. To use the running and cradled (ActiveSync or WMDC connected!) emulator do NOT select an emulator inside VS but a Device. VS does not see the difference and uses the WMDC connected device, regardless of being an emulator or real device.
VS uses DMA to communicate with the emulator, not USB or Serial as with a real device.
Now start your development.
First of all clean your project.Then freshly start the emulator.Right click the project and select build.Then Debug the project.Your project will be started in Emulator (Don't Open the application from your Emulator at this time).
Just check your Emulator Start>File Explorer>My Device>Program Files whether the project has been previously installed.If so uninstall from the Settings> System > Remove Programs. And try re-building application and deploy it.
I have not been able to find any documentation on if you can run applications in debug from a Windows 8 RT based tablet (such as the new Microsoft Surface) like you can on the iPad or Android devices.
Does anyone know if this is possible, and if so (or not), is there any documentation anywhere pointing to such?
Yes, Visual Studio remote debugging supports debugging an app running on an ARM target. You can find more information "What you need to know about developing for Windows on ARM (WOA)."
Visual Studio has the remote debugging tools for working with external devices and other computers. In a Windows Store application project you go to the project properties and click the debug tab. Choose the target device in the dropdown Debug settings (click to see screenshot)
You'll need the setup remote debug service on your tablet and on your dev computer. The devices need to be on the same network subnet. I'm not sure how that will work on the Surface ARM device, as they cannot join a domain. I guess we'll know more once the hardware ships.
Get your remote debugging tools at Visual Studio Downloads.
Jason Zander has a post about working with ARM devices that might be helpful.