-
Notifications
You must be signed in to change notification settings - Fork 93
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
clickEasyApplyButton appears to click whatever button is in the top right of the page #82
Comments
I got the exact same error. It keeps clicking the try premium button. I hope someone has a hot fix for this |
@MoTem @LeenKharboutli try out my fork. I encountered this same issue and fixed it in my local version last year. I've uploaded all my changes now in my fork |
hello [5/1/2024, 14:08:58] Logged in to LinkedIn |
yes im using yours . Thnks for your support. @IggsGrey |
glad it works for you @ammani . Feel free to create an issue over there instead if you ran into trouble |
@IggsGrey no no it didnt work :) I was saying i was using your code but still same issue |
in that case you should open an issue in that repo instead |
The log in and link scraping aspects seem to work fine. However, instead of clicking on the "Easy Apply" button, it clicks on whatever button is in the top right of your LinkedIn page. Before, it was clicking onto LinkedIn Learning, but then I disconnected LinkedIn Learning just to see if that would resolve the problem. Now it clicks on the "Try Premium" button, as it is now at the top right of the page.
I tried several things to debug, but I am not a JS developer by any means.
I attempted going through inspect element to figure out what the selector for the button ought to be, and it appeared that 'button.jobs-apply-button[aria-label^="Easy Apply"]' would do the trick.
The above made no difference. I consulted ChatGPT for a suggestion and tried the following:
Which also did not work. I'm wondering if anyone has encountered the same issue and, if so, what the solution is. Thank you!
The text was updated successfully, but these errors were encountered: