-
Notifications
You must be signed in to change notification settings - Fork 3.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chromeWebSecurity workaround for Cross origin errors no longer working. #1951
Comments
chrome 69 (unstable) seems to be fine |
Is there any proper solution for this problem,I have the same issue. |
Is there any update on this? We have the same issue. Also using chrome 69 seems to not work! |
Nope ..I gave up looking for solution.I am planning in by passing the logging in test for my case.
…________________________________
From: alinadrescher <[email protected]>
Sent: Wednesday, June 20, 2018 7:12:21 AM
To: cypress-io/cypress
Cc: poornimachinnaraj; Comment
Subject: Re: [cypress-io/cypress] chromeWebSecurity workaround for Cross origin errors no longer working. (#1951)
Is there any update on this? We have the same issue. Also using chrome 69 seems to not work!
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub<#1951 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AiDr80qcrKn9rM6vOPpkgTVLiyjrvwsHks5t-jwlgaJpZM4UoZR9>.
|
I have the same problem with update Chrome. |
I looked into this and it's because in Chrome 67 they've begun to randomly roll out Site Isolation. It's currently a Known Isssue documented here that this breaks the I believe that because it is a random rollout then only a subset of users are experiencing this. Did you know that Chrome does A/B experiments and collects the usage? It's likely that either Chrome 69 (currently Canary) has either fixed this or, or on that browser you do not have Site Isolation enabled. TO FIX THIS:Add the We'll go ahead and update the flags to include this by default. IN THE FUTURE:Chrome upgrades should never really affect you this much. For instance, nobody is ever forcing you to upgrade. Whenever newer versions come out that break things in Cypress you should:
You can download Chromium here: https://chromium.woolyss.com/download/ This site also has links to download previous version of Chromium: |
I am correct that this peace should be placed in the plugins/index.js file? If so it did not helped me fixing the memory/Aw, Snap issue. on('before:browser:launch', (browser = {}, args) => {
if (browser.name === 'chrome') {
args.push('--disable-site-isolation-trials');
return args
}
}) |
@neutcomp Yes, see the correct usage here: https://on.cypress.io/browser-launch-api#Usage |
@jennifer-shehane do you mean yes for that it should be placed in plugins/index.js file or that the code is correct? Or both :) Because I used indeed the link you placed to figured out how to implement this args.push functionality. |
You are correct that it should be placed in the You have the code you pasted wrapped in the |
If you wanted to download Chromium versions (say, future versions) here is the link for this: |
Hey, I've disabled Testing cross-domain behavior is critical for my company as we need to test our integration with external services ( like PayPal ). |
me too... tried as suggested here but no luck. |
@UmasankarN try upgrading to |
I'd noticed an error, when I try to search the records .> |
For those who come here after me, the only thing I had to do was modify the {
"chromeWebSecurity": false
} Reference: Disabling Web Security from the Cypress Docs |
@jsjoeio Thanks, your comment did the trick. |
Hello -- I am currently running on Chrome 74 and still having the problem of: I updated my Cypress plugin module.exports = (on, config) => {
on('before:browser:launch', (browser = {}, args) => {
// browser will look something like this
// {
// name: 'chrome',
// displayName: 'Chrome',
// version: '63.0.3239.108',
// path: '/Applications/Google Chrome.app/Contents/MacOS/Google Chrome',
// majorVersion: '63'
// }
if (browser.name === 'chrome') {
args.push('--disable-site-isolation-trials');
return args
}
if (browser.name === 'electron') {
args['fullscreen'] = true
// whatever you return here becomes the new args
return args
}
})
} If you have any tips and or solutions please let me know and I thank you in advance!! |
Hi.. i have added ChromeWebSecurity : false to my cypress.json file and added the above piece of code to plugins index file, still seeing the cross domain errors. Can anyone help me in this please, thanks. |
I am having the same problem. |
I have added the changes to \plugins\index.js and cypress.json and still same outcome. Something as simple as a "login" should not be this difficult. (selenium, puppeteer is much easier) |
cypress.json {"chromeWebSecurity": false} |
index.js module.exports = (on, config) => { on("before:browser:launch", (browser = {}, args) => {
}); |
This bug still happen to for chrome 79 |
This is a very old issue. The exact case of which was closed over a year and a half ago in 3.0.3. If you are experiencing a similar issue, open a new issue with a complete reproducible example. Test code + application to visit so that we can address it. |
Current behavior:
Using
{ "chromeWebSecurity": false }
is not being respected when the test is running since the upgrade from Chrome 66 -> 67.Desired behavior:
Previously the bypass would allow the test to run and pass over the error
Steps to reproduce:
https://github.com/jjp390/cypress-test-tiny
From here, run
npx cypress open
and then run the test spec.js and it will throw the error at the end despite the added file in cypress.jsonVersions
Cypress 3.0.1, OSX 10.13.5, Chrome 67
The text was updated successfully, but these errors were encountered: