-
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
Warn when ProxyMode/ExtensionWhiteList registry setting is detected #4391
Comments
@flotwig I fully agree with your decision. The best solution (from user's and UI/UX's point of view) will be adding a small "We detected ProxyMode key in your registry. Cypress's proxy cannot work properly with Chrome. To fix this issue, please [visit this page | remove the following keys | any other kind of advice that you can give to help people find out what's happening] You can put a link to one of your pages describing the situation and possible solutions. I think that it is not so good to just tell people "hey, just remove those keys", as some people may have no rights to perform such actions, however, this will be the most straightforward solution. Hope this helps :) Keep doing a great job with Cypress! |
The code for this is done in cypress-io/cypress#4405, but has yet to be released. |
Released in |
Cypress fails in strange ways if a ProxyMode policy is set on the user's computer, because it can break Cypress's proxy when running tests in Chrome.
We should:
Relevant issues: #1253 and #4263
Should also detect ExtensionWhiteList/other problematic extension settings.
Relevant issues: #1239, #2494
The text was updated successfully, but these errors were encountered: