Unsupported Chrome Driver - azure-devops

It seems that every time chrome has a new version, I get stuck with this error when running pipeline
System.InvalidOperationException : session not created: This version of ChromeDriver only supports Chrome version 98
Current browser version is 97.0.4692.99 with binary path C:\Program Files\Google\Chrome\Application\chrome.exe (SessionNotCreated)
I've tried install webdriver-manager, it shows the right version, but the problem keeps on. When running locally it all works.
What am I missing here?

You can see the version of chrome which is installed on the pipeline from this link: https://learn.microsoft.com/en-us/azure/devops/pipelines/agents/hosted?view=azure-devops&tabs=yaml
(then select the agent server version you are using)
Then you need to make sure you are using the same version of the chrome driver in your project.
Or use a self hosted agent instead if you want to use a certain version of chrome.

You need to upgrade chrome in your release environment to the latest version, 98.0.
If you are running on a windows VM, for example, that means you need to:
RDP on to the server
load Chrome
view the About Chrome page (chrome://settings/help)
let it upgrade to the newer version
relaunch chrome

Related

Java Error While Running Flutter App on Emulator

After trying to run my flutter app from vs code in android emulator Nexus 5X, I am getting an error which says that I have to setup JDK and I make it's Path Variables for User section and now I am getting a tons of java errors while trying to run my flutter app. Please Help
If you want to run flutter using android java JDK and Android SDK is essential.These are main steps.
Download JAVA JDK from oracle official website and install it
according to your platform(Windows,Ubuntu,Mac,etc.).And set up JDK
too.
Download and install android studio and It will automatically set up
android sdk for our development.
Think your problem is environment path problem or missing JDK.So set up Java JDK first.

Cypress failed to make a connection to the Chrome DevTools Protocol: ECONNREFUSED at TCPConnectWrap.afterConnect

I'm simply trying to run some of the tests in the example folder under Integration and it will not run on Chrome. Runs on Electron and Edge but refuses to run on Chrome and throwing the attached error after unsuccessfully trying.
My version of Chrome is Version 86.0.4240.111 (Official Build) (64-bit)
Current Cypress version is - cypress": "^5.5.0
I reinstalled Google Chrome and it started working. Simple as that.
I just saw this issue on mac and I just had to hard quite Chrome and relaunch it. I didn't have to uninstall and reinstall it.
This issue comes when there is something wrong with your localhost configurations. Please check etc/hosts file.
You can refer to this link for further clarifications.

Can not run my app on emulator - error while loading state for instance 0x0 of device 'goldfish_pipe'

Yesterday I've created Pixel 3 XL device to test my app on emulator. It was working yesterday but today I'm getting these errors when I try to run my app.
14:58 Emulator: C:\Users\Mert\AppData\Local\Android\Sdk\emulator\qemu\windows-x86_64\qemu-system-x86_64.exe: error while loading state for instance 0x0 of device 'goldfish_pipe'
14:58 Emulator: deleteSnapshot: for default_boot
14:58 Emulator: Process finished with exit code 0
for me, I have installed a newer version of HAXM and it worked perfectly
Deleting device from AVD Manager and creating a new one(I created the same one) worked for me
Download the google play version marked in yellow rather google API.
Creating emulator again with image from google play will also make sure reinstallation of HAXM.
I solve this issue within Android Studio SDK Manager, update to a newer version of Android SDK Build-Tools and Intel x86 Emulator Accelerator (HAXM installer), in the HAXM installer wizzard I put 4GB RAM size.
image
In my case I deleted the old devices and downloaded the Google Play play version image and manually changed adb.exe file.
Actually the working HAXM version isn't always the newests, as other answers suggest. I had HAXM version 7.8.0 (latest version ATM) installed on my Windows, but even though I was getting the question error (error while loading state for instance 0x0 of device 'goldfish_pipe'). I had it installed via its own installer, outside Android Studio, because I was getting error trying to install HAXM via Android Studio.
Then I had the idea to uninstall that latest version (7.8.0 ATM) and again try to install the version shown in Android Studio (7.6.5 ATM) via Android Studio itself, and it worked! So I realized the steps I needed to take in order to successfully install HAXM via installer (step 1 shown here) also fixed the problem trying to install it via Android Studio! And finally, after hours and hours of harrassment, I could successfully launch a virtual device on the emulator.
Below is the step for successfully installing HAXM (taken from here):
At last but not least, make sure you have no other virtual machine running! It would throw you at this thread's error.
My case is:
disable Intel x86 Emulator Accelerator (HAXM installer) in Android Studio SDK Manager
uninstall HAXM as a result
enable again Intel x86 Emulator Accelerator (HAXM installer) in Android Studio SDK Manager
install HAXM as a result
recreate emulated AVD
finally works for Me

Unable to automate Hybrid Android mobile app using appium

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.

protractor not connecting to chrome

I am using protractor#3.2.2. It was working fine with chrome all these days. But all of a sudden it is not able to connect to chrome(chromeDriver).
It says
SessionNotCreatedError: session not created exception
It is able to connect to Firefox and Edge.
I am using chromeDriver#2.21
Any ideas about how to fix it?
The chromeDriver 2.21 supports till chrome version 53, But i was using chrome version 54. This is the reason why the chromeDriver is not able to connect to chrome.
Once i downgrade to chrome version 53, everything started to work as expected.
So if you guys face the same issue, check your chromeDriver version and your chrome version.