While launching conf.js file in protractor its giving below error :
ERROR [OsProcess.checkForError] - org.apache.commons.exec.ExecuteException: Execution failed (Exit value: -559038737. Caused by java.io.IOException: Cannot run program "/usr/local/lib/node_modules/protractor/node_modules/webdriver-manager/selenium/chromedriver_87.0.4280.88" (in directory "."): error=86, Bad CPU type in executable)
https://github.com/angular/webdriver-manager/issues/476
Fix will be available soon this weekend. but you will get a workaround by doing this.
As I badly needed to get unblocked - here is a hacky workaround for anyone in similar situation (only for x86_64 macOS). In node_modules/webdriver-manager/built/lib/files/file_manager.js update fileUrl.url around 166:
add below line
fileUrl.url = fileUrl.url.replace(/_m1/, '')
Was facing the similar issue in MacOs Catalina.
This is how it got resolved for me with below versions :
Option 1 :
Download these :
https://chromedriver.storage.googleapis.com/71.0.3578.33/chromedriver_mac64.zip
https://selenium-release.storage.googleapis.com/3.14/selenium-server-standalone-3.14.0.jar
And made the Selenium server UP with this :
java -Dwebdriver.chrome.driver=./chromedriver_71.0.3578.33 -jar ./selenium-server-standalone-3.141.59.jar -port 4444
Option 2 :
Protractor :
Use the below versions :
webdriver-manager update --versions.chrome=71.0.3578.33
webdriver-manager --versions.chrome=71.0.3578.33 start
Got an Error
"Timed out waiting for driver server to start." After running
webdriver-manager update
Resolved it by downgrading to the previous version of webdriver that was working for you.
Steps:
navigate to node_modules/protractor/node_modules/webdriver-manager/selenium/
check if you can see the last chromedriver that you were using before the update
for my case this is chromedriver_86.0.4240.22
since I still have my previous chromedriver, I just Deleted
chromedriver_87.0.4280.88
chromedriver_87.0.4280.88.zip
in node_modules/protractor/node_modules/webdriver-manager/selenium/update-config.json
I changed all instances of chromedriver_87.0.4280.88 and replaced with chromedriver_86.0.4240.22
Run your tests.
Incase you dont know what was the last version that worked for you, you can try
webdriver-manager update --versions.chrome=86.0.4240.22
or look for a version here
This is what worked for me:
Update the protractor version to current stable version: "protractor": "^7.0.0", npm install was the way to go for me, yours will be similar
Update the webdriver: webdriver-manager update with or without sudo is the right command as stated in other answers
Run the webdriver manager with the current chrome version, this is the command that I use for application: webdriver-manager start --versions.chrome=88.0.4324.96 as my chrome is currently at that version, replace it with your chrome's version (87.0.4280.88 as per the question)
Related
I have this problem for a few day and I have noticed that chromedriver version has been upgraded automaticlly to the 86. So I am guessing I need to downgrade it to 84. But I am not sure. May be I should upgrade something but I do not know what. My webdriver-manager vesrion is "webdriver-manager": "^12.1.7",
Any hints, please?
Try the below command to resolve the webdriver update issue
node node_modules/protractor/bin/webdriver-manager update --versions.chrome=<desired chrome version> --standalone --gecko=false --ignore_ssl
Try this if you want to run on chrome browser.
In protractor sometime gets Error: ”Session not created ” because of not supported/incompatibility driver version for current browser version.
I have tried below steps:
Step 1: Delete selenium folder inside webdriver-manager .
All browser driver should be presented in this folder.
Path: ..\node_modules\protractor\node_modules\webdriver-manager\selenium
Step 2: node node_modules/protractor/bin/webdriver-manager update - This will download all browser driver versions inside selenium folder.
Or else you can update webdriver-manager with specific version you want.
node node_modules/protractor/bin/webdriver-manager update --versions.chrome=XX.X.XXXX.X
I am junior QA Tester, started working with Cypress and IDE Visual Studio, after updating Cypress 5.2.0, I got a strange error like the following:
It looks like this is your first time using Cypress: 5.2.0
✖ Verifying Cypress can run /Users/viktoriiahanke/Library/Caches/Cypress/5.2.0/Cypress.app
→ Cypress Version: 5.2.0
Cypress failed to start.
This is usually caused by a missing library or dependency.
The error below should indicate which dependency is missing.
https://on.cypress.io/required-dependencies
If you are using Docker, we provide containers with all required dependencies installed.
----------
Command was killed with SIGKILL (Forced termination): /Users/viktoriiahanke/Library/Caches/Cypress/5.2.0/Cypress.app/Contents/MacOS/Cypress --no-sandbox --smoke-test --ping=563
----------
Platform: darwin (19.6.0)
Cypress Version: 5.2.0
I have already tried to delete Cypress and install it with npm from the beginning, but Cypress itself is working, when I download it manually , but when I try to start it in console or in Visual Studio Console it is not opening, writing me that I miss dependencies like above.
Did anyone have such problem before?
Run this command in the terminal export NODE_TLS_REJECT_UNAUTHORIZED=0
and then try installing again.
I think it had been updated from a previous version, 3.1.3. Go into cache and delete all versions of cypress then re-install.
Maybe that there are missing some vital folders/files like integration, cypress.json... Try to run the 'npm install' command in the terminal for installing the dependencies.
Also, maybe if you start from an existing project, it will be fine (run npm install command also).
I keep using vscode debug for long time. But it began to fails to use debug from yesterday.
It reports that The terminal process failed to launch: A native exception occurred during launch (File not found: ).
I can use powershell in terminal.
I have tried solution in (https://code.visualstudio.com/docs/supporting/troubleshoot-terminal-launch), but none of them works.
Code -version: 1.47.3
Operating System version: windows 10 1909 build 18363.959
all extensions：
albert.TabOut
christian-kohler.path-intellisense
CoenraadS.bracket-pair-colorizer-2
Equinusocio.vsc-community-material-theme
Equinusocio.vsc-material-theme
equinusocio.vsc-material-theme-icons
eryouhao.brackets-light-pro
formulahendry.code-runner
formulahendry.terminal
Gruntfuggly.todo-tree
HookyQR.beautify
James-Yu.latex-workshop
kisstkondoros.vscode-gutter-preview
manasxx.background-cover
marlosirapuan.nord-deep
MS-CEINTL.vscode-language-pack-zh-hans
ms-python.python
ms-python.vscode-pylance
ms-vscode.cpptools
naumovs.color-highlight
niudai.vscode-zhihu
nnthink.aixcoder
redhat.java
skacekachna.win-opacity
sldobri.nord-5-stars
TabNine.tabnine-vscode
VisualStudioExptTeam.vscodeintellicode
vscjava.vscode-java-debug
vscjava.vscode-java-dependency
vscjava.vscode-java-pack
vscjava.vscode-java-test
vscjava.vscode-maven
vscode-icons-team.vscode-icons
wix.vscode-import-cost
yzhang.markdown-all-in-one
zhuangtongfa.material-theme
setting.json:
"terminal.integrated.shell.windows": "C:\\WINDOWS\\System32\\WindowsPowerShell\\v1.0\\powershell.exe"
In my case this problem arising after updating VS Code version to 1.54.3 on Ubuntu 18.04.
This problem is resolved by restarting VS Code after the update.
Yep, that's kinda what my problem was...PS had been blocked at a system-admin level.
Make sure that you can actually run PS from the command-line or start window.
Win10 popup
I fixed it by change "terminal.integrated.inheritEnv" to false in setting.json.
I also had the same issue and asked the question one week before yet didn't get solution.
here is link of my question
[link]Visual Studio (VS-code) code terminal is failed to launch
1 solution i got:
the issue arises when you delete some of it's files before by mistake and you don't know try to remember that or simply recover your pc to 3 weeks ago atleat so all files will be placed suitably.
I had the error. To fix it, I looked at all the terminal settings in VSCode and checked out the ones that weren't set to the default value. Eventually, I found that the path to my PowerShell had changed to the preview version I had installed. Reverting this to its default got it working again. Hope this helps someone.
I am getting the following error below when trying to start webdriver-manager.
It is working yesterday, after restarting it today, I am now getting a certificate error.
I enter --ignore_ssl, added proxy/https-proxy on User Variables and I already tried running the cmd as an administrator.
Error:
C:\Users\<user>\AppData\Roaming\npm>webdriver-manager start --ignore_ssl
events.js:160
throw er; // Unhandled 'error' event
^
Error: unable to get local issuer certificate at Error (native)
at TLSSocket.<anonymous> (_tls_wrap.js:1092:38)
at emitNone (events.js:86:13)
at TLSSocket.emit (events.js:185:7)
at TLSSocket._finishInit (_tls_wrap.js:610:8)
at TLSWrap.ssl.onhandshakedone (_tls_wrap.js:440:38)
When updating, I was able to update successfully without an error.
Fixed in webdriver-manager 12.0.5+:
This was an actual issue with webdriver-manager and was tracked as issue #229. On start, webdriver-manager would check the cache and if the cache was old, it would replace it. The problem identified above is that the ignore_ssl and proxy flags were not being passed.
The real issue is that webdriver-manager start should not be making any web requests. Removing web requests removed the need to pass the ignore_ssl and proxy flags around. So if a user were to test their web app locally on an airplane, starting the selenium server should still work.
Anyway, this has been resolved in PR #232 and we should have a new release (12.0.5) later today.
Update:
webdriver-manager version 12.0.5+ should have this fixed. The latest as of this update is 12.0.6. You can check what version you have installed with webdriver-manager version.
webdriver-manager version
webdriver-manager: using global installed version 12.0.5
[08:18:51] I/version - webdriver-manager 12.0.5
Troubleshooting
Potential errors could include having an old installed global version although you have installed a project dependency with the correct webdriver-manager version.
How do I know start makes no web requests? Well, other than unit tests, I have tried this out by turning off wifi and trying webdriver-manager start. If start fails for you at this point with no internet, please check your version.
webdriver-manager start --ignore_ssl
this will work for you.
Trying to run a Protractor test but am receiving the following command line error when trying to test in Chrome.
UnknownError: The process has not exited yet therefore no result is available ...
The test successfully runs in Firefox, i.e. when the protractor.conf.js file is set as such:
capabilities: {
'browserName': 'firefox'
}
I'm currently using ChromeDriver 2.10, which seems to have something to do with the issue (https://github.com/angular/protractor/issues/1424). However, I'm unclear how to configure Protractor to use a different version of ChromeDriver.
So, reverting to ChromeDriver 2.9 was as easy as downloading it from here (http://chromedriver.storage.googleapis.com/index.html?path=2.9/) and extracting the zip into /usr/local/lib/node_modules/protractor/selenium.
That fixed the immediate issue of not being able to run the test in Chrome. Still waiting on a fix for 2.10, I suppose.