My protractor scripts were running fine on Chrome V62 & chromeDriver 2.35. My browser got updated to v64 and from then on, i m experiencing the wierd behaviour where my browser opens with "data.;" & then hangs for 10 min and then proceeds with execution.
I updated my chromeBrowser to 2.36 & also selenium server to 3.12.0. on running "webdriver-manager update" it says: all are uptodate. Not sure what is causing the issue.
Versions:
Node: 8.8.1
protractor : 5.3
Chrome: 64
ChromeDriver:2.36
seleniumserver: 3.12.0
& directConnect:true.
All of the versions is samefrom the begining, except for chromeDriver & chrome. Can canyone tell me what went wrong please.
Related
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
When I want to inspect a page listed on chrome://inspect page on a remote Pixel 4 with OS version 11, I get a white page with just 'HTTP/1.1 404 Not Found' shown.
I uninstalled all updates from Android Chrome, went down to version 83, and remote debugging started working again.
I have the same problem with current versions of Chrome beta/dev/canary.
Is this only a problem on my device, or a general problem? Any way to get remote debugging working with Chrome 89?
Thanks,
Michael
It seems you can't get it working on Chrome 89 for now because this is a general problem. I got the same issue on Vivaldi 3.7 which runs Chromium 89. The only option for now is rolling back to previous working release.
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.
I am using eclipse, Appium 1.6.4 and Android Studion with Android 7.0 also tried with 6.0.
I run my automated test and it executes, it connects to the device, it opens the chrome browser but then doesnt navigate to the google url using the driver.get(...) method it just says data;, . I dont get any errors until it eventually times out and tries running it again.
Any help would be appreciated as ive tried a few things and got nothing.
Thank you.
Whats are the Protractor Supported versions of Firefox, IE and Safari?
My test does not run in Firefox latest version.
#High level Protractor is just a wrapper around webdriver. It depends on browser versions you want to test en the webdrivers for that browsers you have downloaded with webdriver-manager as said by #alecxe.
Currently there are some known issues with the webdrivers that can also be found on the Protractor GitHub:
Firefox latest has problems with Angular2 apps, see this link, as far as I can remember Protractor worked till Firefox 47, it broke due to problems in de webdriver of Firefox from version 48-50 and it started working from 51, but not for Angular 2.
IE11 works
Microsoft Edge, see this, as far as I can see still not stable on version 14.
Safari 9, works, but it's with the old Safari Driver, it misses a lot of user interactions like Tabs, mouse events and so on.
Safari 10, I've heard that it works with the latest version of the Safari webdriver, don't heave experience with it, see also here for a guy who had problems with it but got it working.
Chrome, should work with all latest versions if you always keep you ChromeDriver up-to-date.
Hope this gives you a good idea!
Protractor depends on the webdriver-manager package which now, since version 12.0.0, installs the latest versions of selenium-webdriver, iedriver, chromedriver and geckodriver.
Then, to determine which browser versions are supported, you need to see what driver version was installed by the webdriver-manager:
$ webdriver-manager status
and then look up what browser versions your installed driver version supports.
My test does not run in Firefox latest version.
In your case, you might be experiencing this problem:
Webdriver-manager will now by default grab the latest versions of all
binaries (standalone, chromedriver, iedriver, gecko driver). Use the
--versions.(binary name) to pin to a specific version. Selenium standalone 3.0.1 has a bug which prevents it from working with any
version of FireFox. We have tested version 3.0.0-beta4 and know that
it works with FireFox 51, and we expect that the 3.0.2 release will
also work.
Which currently means that you should be able to fix it by running:
$ webdriver-manager update
Or, you may also try the directConnect mode.