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

Login problem #1

Open
schilke opened this issue Jun 24, 2023 · 6 comments
Open

Login problem #1

schilke opened this issue Jun 24, 2023 · 6 comments

Comments

@schilke
Copy link

schilke commented Jun 24, 2023

Looks like I'm not able to login.
During Playwright installation I got the message "BEWARE: your OS is not officially supported by Playwright; downloading fallback build." (Linux Mint 19.3 here - based on Ubuntu Ubuntu 18.04 LTS)
Not sure if this has to do with the issue, though.
image

@vikas5914
Copy link
Owner

@schilke, which browser got opened?

@vikas5914
Copy link
Owner

@schilke I have deployed some new code, try that. (don't forget to do npm install again)

@vikas5914
Copy link
Owner

@schilke Please check now; I have added the option to use chrome or edge instead of Chorium.

@markcs
Copy link

markcs commented Aug 7, 2024

I have this same issue. I have tried with both Chrome and Chromium. I am using the script on Ubuntu, but I can't get it to work. The same error as above.

Any ideas?

@lucasengel
Copy link

lucasengel commented Oct 16, 2024

@markcs I've switched to chromium and things seemed to work fine. You can edit the channel entry in setup.js, switching from chrome to chromium

EDIT1: You'll also need to authenticate using your password instead of keypass (in case you enabled that in your account)

EDIT2: I have not seen this int he instructions but reading Playwright's docs I learned you should run this to create the below command for persisting your authentication:

mkdir -p playwright/.auth
echo $'\nplaywright/.auth' >> .gitignore

@purarue
Copy link

purarue commented Oct 20, 2024

Just to share what worked for me, did not need to update anything with playright/.auth to persist authentication, the session folder seemed to handle that fine.

Changed to chromium and added a playright flag that removes the navigator.webdriver flag so its less detectable by google login (not sure if this was necessary since Im using chromium and not chrome, but doesnt seem to break anything).

Instead of modifying both setup.js and index.js, I just added a prompt in index.js telling the user log in and press enter before starting, I skipped using setup.js altogether and ran this in non-headless mode like node index.js --headless=false

Heres the diff: seanbreckenridge@799693c

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants