joaosilvalopes / linkedin-easy-apply-bot

MIT License
237 stars 87 forks source link

No element found for selector: #session_key #75

Open babaz8 opened 1 year ago

babaz8 commented 1 year ago

No element found for selector: #session_key at assert (/Users//linkedin-easy-apply-bot/node_modules/puppeteer-core/src/util/assert.ts:29:11) at IsolatedWorld.type (/Users//linkedin-easy-apply-bot/node_modules/puppeteer-core/src/common/IsolatedWorld.ts:348:11) at processTicksAndRejections (node:internal/process/task_queues:95:5) at async login (/Users//linkedin-easy-apply-bot/login/index.ts:17:3) at async /Users//linkedin-easy-apply-bot/scripts/apply.ts:45:3

ismaelrodino2 commented 1 year ago

in fetchJobLinksUser.ts before await page.type(selectors.keywordInput, keywords); , add await page.waitForSelector(selectors.keywordInput); .

AnthonyHeinrichs commented 1 year ago

I also have another suggestion to work around this as the above solution wasn't helping and the issue for me as occurring in login -> index.ts.

The selectors specified in selectors -> index.ts wasn't being found so I made the following changes to the login process:

Changed index.ts:14 await page.goto('https://www.linkedin.com', { waitUntil: 'load' });

to await page.goto('https://www.linkedin.com/login', { waitUntil: 'load' });

Updated my selectors in selectors -> index.ts from line 25 to:

// Login captcha: "#captcha-internal", emailInput: "#username", passwordInput: "#password", loginSubmit: "button[class*='btnprimary--large frombutton--floating']", skipButton: "button[text()='Skip']",

If you're still running into the issue, try what ismaelrodino2 mentioned above and set the wait for selectors for login selectors etc on the login selectors: await page.waitForSelector(selectors.emailInput);

GDemay commented 2 months ago

I have the same issue

mrchameleon commented 2 months ago

Using @AnthonyHeinrichs comment, I was able to get the script working, to login and search the job list. However, it is not applying, and there is no error in console.

I'm going to investigate the code and see if it is a changed element name or something. The chat window is popping up and getting in the way, I wonder if that is part of the problem.

alexwastaken commented 1 month ago

same with @mrchameleon, has anyone found a solution?

ctoxyz commented 3 days ago

image

Same issue

ctoxyz commented 3 days ago

I tried this >

in fetchJobLinksUser.ts before await page.type(selectors.keywordInput, keywords); add await page.waitForSelector(selectors.keywordInput);

still got :

image