This question already has answers here:
Closed 11 years ago.
Possible Duplicate:
Android Emulator is not starting showing " invalid command-line parameter"
I installed the SDK for android, but the Emulator will not start.
I attempt to start the Android Emulator but get this error.
invalid command-line parameter: Files\Android\android-sdk\tools/emulator-arm.exe.
Hint: use '#foo' to launch a virtual device named 'foo'.
please use -help for more information
As you can see from the error message; the file path has a Unix forward slash in it and I am running a windows system.
I need help fixing this problem and I have already tried reinstalling the SDK, which did not work.
Thanks for your help.
John is correct. I was having the same problem and error. I uninstalled the Android SDK and re-installed directly under my 'C' drive as 'C:\Android'. Once the install was complete, I ran the update for all possible packages. At that point I ran the emulator and it ran perfect.
Since I use Windows 7 64-bit, the default location for 32-bit applications is 'C:\Program Files (x86)\'. The multiple spaces in the primary folder name was causing the trouble.
Just make sure, if you are using Eclipse, to go back into Eclipse and update the file path for the SDK or Eclipse won't work correctly.
Related
I know this message has been already asked before but none of the answers has fixed my issue,
The error message:
I have already tried disabling the hotspot of my emulator (which is a Pixel XL API 30) but it doesn't work. I have also tried restarting my pc, IDE and emulator and also changing my IDE from vs code to Android Studio but the error doesn't go away. I am new to flutter and I don't want to give up at the start!
Disable your mobile hotspot. If you use windows 11 that was my error try, will run normally easy like this.
For me, it was the Windows Hotspot Wifi as "#Salah dine Maham" said.
As I know it is related to a gradle issue (shows up from about gradle v6.3), I went to the
android/gradle/wrapper/gradle-wrapper.properties
I updated the distributionURL into :
distributionUrl=https\://services.gradle.org/distributions/gradle-7.1.1-all.zip
You "may" need to update the gradle plugin on the android project.
And now you can debug again freely through Windows Hotspot wifi.
So, as I said I couldn't find any solutions but here it is:
delete ANY VMware processes or, if you can, unistall VMware and use virtualbox instead, even if vmware is not running it will confict with other emulators.
Credits
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 attempting to run an iPhone app in the Trigger Toolkit, but I keep getting "Unable to locate GDB" in the console, several seconds after "Connecting to remote debug server" . I've updated xcode, installed gdb separately through homebrew, and am able to run it (gdb) through the command line.
Thanks in advance for any relevant advice!
I'm guessing you're using a pre-v2.0.1 platform version here, and that you've updated to Xcode 5?
I was able to reproduce this error in that configuration. Xcode 5 doesn't support GDB, which we were previously using to communicate with the app running on your device.
If updating to use newer platform versions isn't an option for you, you could use an older installation of Xcode (you can have several versions installed as siblings), and use xcode-select to point us at it, e.g.:
sudo xcode-select --switch /Applications/Xcode4.6/Xcode.app
I thank you all for reading this lengthy question. It's really important and I will appreciate it if you can assist me :)
The problem -------
I am have been using the Windows 7.1 SDK for about two months now. The emulator has worked without any problem so far. However, today, it began displaying this error (The saved state (Name of File).dess is corrupt. Please delete the corrupted saved state file and then retry). I had not made any significant changes to my project code, or moved any files. I had just added some Visual State animations for a button.
As it suggested, I went ahead to delete the file. I then started debugging again. However, the emulator now opened and displayed the message (Windows Phone Emulator is doing a complete OS reboot). This message was displayed for a very long time. I closed the emulator and project. Since then, I have been unable to use the emulator. I am able to code normally in Visual Studio, but I cannot test my application.
What I have tried ------
I read up on this issue and found many others who faced the same emulator issue. Following their suggestions, I have run one repair of the Windows Phone SDK 7.1. I have also tried uninstalling and then re-installing the SDK 7.1 once.
System Specifications -----
I am using Visual Studio Express 2010 for Windows Phone (Windows 7 64 bit)
I have downloaded the Windows Phone SDK 7.1 from this link: http://go.microsoft.com/fwlink/?LinkId=258412
I have read that this issue might be because of some hardware incompatibility. However, I think my machine is compatible with the emulator. Here is some information.
DirectX Version: DirectX 11
8GB RAM
Driver Model: WDM 1.1
Additional Information:
I have read that installing the 'January Update' might fix this issue. I tried downloading the update from this link: http://www.microsoft.com/enus/download/details.aspx?id=23854
However, the installer said that the update is not compatible with the product/version of the product I am using.
Usually the Repair function of the WP7.1 SDK is enough to fix all the issues. It runs the generation of the saved state of the emulator again.
Please try to delete files in %ProgramData%\Microsoft\XDE folder first (make sure you backup them somewhere else.), then run the emulator. If the emulator runs with a message "Windows Phone Emulator is doing a complete OS boot," let it boot. It takes some time though. This way you will know that the emulator actually can run on your computer. This won't generate a new saved state image, but the emulator should at least load.
Next, try installing WP7.1.1 SDK update from http://www.microsoft.com/en-us/download/details.aspx?id=29233. This update also installs additional 256MB emulator image besides the original 512MB image. It also generates emulator's saved states in the process, potentially fixing the issue.
If everything fails, then try these instructions to fix the saved state of the emulator:
Uninstall WP7.1 SDK
Manually delete these folders:
%ProgramData%\Microsoft\XDE
%LocalAppData%\Microsoft\XDE
Install WP7.1 SDK again.
Install WP7.1.1 SDK update: http://www.microsoft.com/en-us/download/details.aspx?id=29233.
Edit:
Btw, have you tried to reboot your computer? Once this fixed the issue for me.
Alright, I managed to solve this problem.
I reinstalled Windows and downloaded the SDK 7.1 again. The emulator works fine now!
#Paulos, thanks for helping!
I had the same problem for a long time. Try this:
Start up Visual Studio 2010, but before you start debugging, click on the tabs of all the open pages so that all the xaml pages and code behind pages can load.
I noticed it when I opened Visual Studio, but the first open page was a code behind page and not an xaml page, so when I first clicked on the tab of a xaml page, of course, it took some time to load the xaml page into the editor. However, when that and one or more open xaml pages were also loaded, the emulator started without the error message.
I tried to run the directx samples from ..\Windows Mobile 6 SDK\Samples\PocketPC\CPP\win32\directx\d3dm\tutorials on a Samsung Omnia and on the emulator and it doesn't work because of a deployment error.
I am using Microsoft Visual Studio 2008 and have installed Windows Mobile SDK Standard and Professional refresh.
The device is correctly plugged in and set up for active sync (I know this because other samples work, also a creating Win32 smart device application and running it works).
When I try to run a directx sample application it compiles without errors but the message:
" There were deployment errors, Continue? Yes/No" appears
If I manually copy the application from the debug folder to the device and run it from there, it works.
The same deployment error message appears if I try it on an emulator. Other applications are deploying successfully.
Is there any way to make the deployment work? Maybe there is an obscure option I need to set...
What I do is:
Connect the Mobile device to the PC,
Open Visual Studio 2008,
Open a directx sample project,
Click Run (in Debug or Release mode).
The problem with the deployment is that the file msvcr80.dll could not be found.
It was specified at the deployment options as an additional file "Project->Properties->Configuration Properties->Deployment" then "General->Additional files"
with the paths msvcr80.dll|$(BINDIR)\$(INSTRUCTIONSET)\|%CSIDL_WINDOWS%|0;
Removing it makes the deployment successful. I have only tested this on a Windows Mobile 6.1 device and with the D3DM reference driver on an WM6.1/WM6 emulator.
What I haven't figured out is where does $(BINDIR)\$(INSTRUCTIONSET) point to.
Also I don't know why msvcr80.dll is in the addition files if it is not actually needed.
Is there actually a msvcr80.dll compiled for Windows Mobile platform on an ARM cpu?
I was able to resolve this issue after doing some low-level Sysinternals Debugging. It was trying to deploy NETCFv35.Messages.EN.cab to the device and in my case it was deleted for some reason. Re-installing .NET CF fixed the issue for me. Wish VS 2008 said what file was missing instead of a generic message. Hope this helps you too.