-
Notifications
You must be signed in to change notification settings - Fork 102
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
No element found for selector: #session_key #75
Comments
in fetchJobLinksUser.ts before await page.type(selectors.keywordInput, keywords); , add await page.waitForSelector(selectors.keywordInput); . |
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 to Updated my selectors in selectors -> index.ts from line 25 to: // Login 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: |
I have the same issue |
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. |
same with @mrchameleon, has anyone found a solution? |
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
The text was updated successfully, but these errors were encountered: