Skip to content
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

Log In With GitHub Gives Blank Screen #4337

Closed
alexlee-dev opened this issue May 29, 2019 · 20 comments

Comments

3 participants
@alexlee-dev
Copy link

commented May 29, 2019

Bug

Current behavior:

Able to click Log In With GitHub, but a blank window appears and never loads the GitHub login. This is behind a corporate proxy, but the proxy configuration has already been set up.

LogIn

LogInBlank

Desired behavior:

Ability to log in to GitHub to see the Dashboard Service.

Steps to reproduce: (app code and test code)

  1. Open Cypress v3.3.1
  2. Click "Runs" tab.
  3. Click LogIn with GitHub.
  4. Get new window popup with blank screen.

Versions

Cypress: v3.3.1
OS: Windows 10

@flotwig

This comment has been minimized.

Copy link
Member

commented May 29, 2019

Can you share a screenshot of your proxy settings from Cypress as well as a copy of the debug logs when you try to do this?

@alexlee-dev

This comment has been minimized.

Copy link
Author

commented May 29, 2019

@flotwig sure!

Screenshot of proxy settings:
proxy settings

Debug Logs:
loginIssue.log

I can see that a new window was opened with type: 'GITHUB_LOGIN'. It was successfully able to create a proxied socket to https://api.cypress.io/auth with my proxy. It receives a response containing a GitHub login OAuth url. It then changes the user agent to Mozilla/5.0.

@alexlee-dev

This comment has been minimized.

Copy link
Author

commented May 30, 2019

@jennifer-shehane I'd love to provide whatever additional information is needed.

I've attached a copy of debug logs. What info can I provide?

@flotwig

This comment has been minimized.

Copy link
Member

commented May 31, 2019

@alexlee-dev I've taken a look at the DEBUG logs you provided; unfortunately, there's nothing I can see that would cause this problem. Does GitHub login work for you in 3.2.0?

@alexlee-dev

This comment has been minimized.

Copy link
Author

commented Jun 2, 2019

I'll give it a go on Monday when I'm back at the computer and report back here.

@alexlee-dev

This comment has been minimized.

Copy link
Author

commented Jun 3, 2019

Since I'm behind a proxy, I've been using the CDN to download the latest version and point my CYPRESS_INSTALL_BINARY to that .zip. How can I download previous versions in a zip from the CDN? I tried to download the asset from the GitHub releases page, but the file is suspiciously small. @flotwig

@flotwig

This comment has been minimized.

Copy link
Member

commented Jun 3, 2019

@alexlee-dev You should be able to install older versions of Cypress like you would install any project:

npm i cypress@=3.2.0

If you don't have HTTP_PROXY environment variables set up, you'll need them so that npm install can download the Cypress binary correctly. Here are some instructions for doing that on Windows.

Failing that, older versions are available from the download server at certain URLs. Try https://download.cypress.io/desktop/3.2.0?platform=win32

@alexlee-dev

This comment has been minimized.

Copy link
Author

commented Jun 3, 2019

@flotwig Thanks. Yeah just using npm i cypress@whatever even with the HTTP_PROXY and HTTPS_PROXY set up doesn't work for me for whatever reason.

The extra bit on the CDN url is great though. Thank you. Will report back if 3.2.0 allows me to log in.

@alexlee-dev

This comment has been minimized.

Copy link
Author

commented Jun 3, 2019

v3.2.0 does not seem to read my HTTP_PROXY / HTTPS_PROXY environment variables like v3.3.1 does. When I click the "Runs" tab, it times out trying to contact the api.

timeout

@flotwig

This comment has been minimized.

Copy link
Member

commented Jun 3, 2019

Proxy support was added in 3.3.0, though some user's environments mean that a proxy is not strictly required to access the Internet, which is why downgrading sometimes appears to fix proxy issues. Looks like it didn't help here.

@alexlee-dev

This comment has been minimized.

Copy link
Author

commented Jun 3, 2019

Gotcha. Any other suggestions for something I can try on my end? I'll be spending some time today poking through the source code trying to see what I can do.

@flotwig

This comment has been minimized.

Copy link
Member

commented Jun 3, 2019

@alexlee-dev Try it without a proxy configured if there is any way to reach the Internet without a proxy on your computer. I'm fairly sure the issue lies somewhere in there.

@alexlee-dev

This comment has been minimized.

Copy link
Author

commented Jun 3, 2019

Unfortunately, there is no way for me to access the internet without a proxy on this computer. (Super proxied work setup)

@alexlee-dev

This comment has been minimized.

Copy link
Author

commented Jun 3, 2019

So far, I've been able to see that even when the proxy is configured and it lets me get to the "Runs" section, images are not loaded. If I force the devTools option to true, I see the failing network requests for the images with the error: net::ERR_NO_SUPPORTED_PROXIES.

Still digging...

@flotwig

This comment has been minimized.

Copy link
Member

commented Jun 4, 2019

Could be related to this: electron/electron#12443

Does your proxy server require auth in the URL? http://user:pass@proxyserver.com...

@alexlee-dev

This comment has been minimized.

Copy link
Author

commented Jun 4, 2019

I don't believe so, because I've been able to use the proxy with other applications fine with no authentication in the url. http://proxyserver.com:portNumber

@alexlee-dev

This comment has been minimized.

Copy link
Author

commented Jun 4, 2019

Does anyone know if having localhost in the proxy bypass list would be causing this? i.e. does Cypress make any calls to localhost in order to hit the Cypress API? If it wasn't going through the proxy, that might do it.

@flotwig

This comment has been minimized.

Copy link
Member

commented Jun 4, 2019

localhost should always be in NO_PROXY, but that shouldn't be causing this issue anyways since this doesn't rely on localhost being reachable.

@cypress-bot

This comment has been minimized.

Copy link

commented Jul 9, 2019

The code for this is done in cypress-io/cypress#3616, but has yet to be released.
We'll update this issue and reference the changelog when it's released.

@cypress-bot

This comment has been minimized.

Copy link

commented Jul 9, 2019

Released in 3.4.0.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.