I want to automate test a basic Hybrid Mobile Application running in Android.I am able to launch the app in emulator but not able to enter the text in the login screen.
Getting error as
"Exception in thread "main"
io.appium.java_client.NoSuchContextException: An unknown server-side
error occurred while processing the command. Original error: No
Chromedriver found that can automate Chrome '53.0.2785'. See
https://github.com/appium/appium/blob/master/docs/en/writing-running-appium/web/chromedriver.md
for more details. "
Please help me resolving this!!!!!
If you see chromedriver.exe change log you will get the version you require for hybrid app automation. The browser used in your device have versin 53+
See this url http://chromedriver.chromium.org/downloads [check ChromeDriver 2.24 details] it says it supports browser with version 53+. Get this exe from https://chromedriver.storage.googleapis.com/index.html?path=2.24/
How to connect with Appium -
If you are using appium desktop, it gets installed as windows application in program files folder. Now location of chromedriver.exe it uses is as mentioned below.
C:\Program Files (x86)\Appium\resources\app\node_modules\appium\node_modules\appium-chromedriver\chromedriver\win\chromedriver.exe [This location may be bit different in your case]
Replace above location chromedriver from downloaded chromedriver.exe(from step2)
Note - Ideally automation should work without throwing exception. Incase still it doesn't work then try 1+ or 1- version of 2.24
You got everything you need in exception message:
Go here https://github.com/appium/appium/blob/master/docs/en/writing-running-appium/web/chromedriver.md
and read explanation on compatibility.
No Chromedriver found that can automate Chrome '53.0.2785'
Appium was not able to get chromedriver for your emulator that have Chrome 53.0.2785
So the first solution is to get Chromedriver v2.26 and add absolute path to binary as chromedriverExecutable capability:
1) download chromedriver_win32.zip from the link above and unzip
2) in your code add capability with the path to chromedriver.exe:
DesiredCapabilities caps = new DesiredCapabilities();
...
caps.setCapability("chromedriverExecutable", "/abs/path/to/chromedriver.exe")
If you get new emulator, first check what browser version is preinstalled and try to upgrade.
This is the error I'm getting.
The following unexpected error occurred during bootstrapping stage 'Connecting to the device '192.168.1.3'.': MissingMethodException - Method not found: 'Boolean Microsoft.Tools.Connectivity.RemoteDevice.Ping()'.
Maybe you are using a wrong windows SDK witch could be installed by VS custom installing. You can try uninstall "Windows Software Development Kit" on "program and feature", and install one here:
https://developer.microsoft.com/en-US/windows/downloads/windows-10-sdk
Maybe you need fix your solution by missed feature when you open your project again.
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've built my application as an x86 native app, and I've ran it on Genymotion. The problem occurs when I try to debug from Eclipse. In the console view, I get the age old:
gdbserver output:
run-as: exec failed for lib/gdbserver Error:No such file or directory
Verify if the application was built with NDK_DEBUG=1
It all works fine with ARM builds though. I checked that the x86 gdbserver is getting included in my .apk lib/x86/gdbserver. I've also read that the x86 versions of android include a gdbserver locally anyway, so not sure what the point of all that is.
I've been able to manually attach the included gdbserver using adb shell, and then get Eclipse to attach to it remotely using this is a starting point: How to get ndk-gdb working on Android?
It doesn't mention anything about x86 or Genymotion though. Unfortunately, it's tedious, and it's seemingly useless since it doesn't load any symbols (though that's probably because of my ignorance.)
Is there any guidance for making this setup, using Eclipse and Genymotion to debug native apps, work?
Sadly, this is due to a bug in Genymotion v2.2
It will be fixed on our next release (I work for Genymotion).
You are right, gdbserver is not deployed from the apk, and this is why it doesn't work.
You can find here a patch to apply that will fix this apk deployment bug for Genymotion KitKat devices created with Genymotion 2.2: native-debug-fix.kitkat.zip
Warning this patch is only for:
Kitkat (Android 4.4.2) devices
created with genymotion v2.2
Don't apply the patch on other devices, it will brake things.
to apply the patch, simply drag n'drop the zip file on genymotion.
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.