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.
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'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.
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.
I have an ionic (version 1.7) app and I can start it in the Android Studio 2 emulator. Unfortunately I can not reach my backend server at http://10.0.2.2:8181/, I always get a 404 not found error. I also tried using Genymotion (with ip http://10.0.3.2:8181/) but I still get a 404. Did anything change in the new versions or does anyone have an idea what to do?
Check to see if the URL is valid. Can you access the server in your browser?