Chrome headless does not work with Re-direct (OAUTH2)

Question

When I run my protractor project normally, everything is fine, but in headless mode, it does not work, times-out waiting for the first element I need.

I feel that because the page redirects due to OAUTH2, in headless it fails.

I have tried '--ignore-certificate-errors' but this has not worked for me. I have also tried '--disable-dev-shm-usage' without success. I have tried other ones like ignore ssl errors, localhost, etc, nothing seems to work.

Has anybody run into this issue?

Did you try to get a screenshot to see where exactly the browser stops? — Jens Dibbern, Apr 12 '19 at 23:43
Hi @JensDibbern Yes, I just did that, thank you. It turns out my app threw a pre-defined "Unsupported Browser Type" — snikt, Apr 15 '19 at 20:12

score 1 · Answer 1 · answered Apr 15 '19 at 21:10

1

Solved it by changed --user-agent value in chrome args

answered Apr 15 '19 at 21:10

snikt

581
4
11
27

Chrome headless does not work with Re-direct (OAUTH2)

1 Answers1