Closed matthewalampe closed 1 year ago
Is there a way to maybe refresh the page after applying to make the elements not stale? I keep trying the self.driver.refresh() but it gets stuck in a refresh loop.
same issue here, still looking into the issue. any update would be appreciated @voidbydefault
osama3101995: same issue here
matthewalampe: stale element reference: stale element not found
You have to understand what are stale elements
. Read [this comment] (https://github.com/voidbydefault/EasyApplyBot/issues/11#issuecomment-1672632773)
Keep the browser window used by bot 1) "maximized", and 2) leave it alone (do not open tabs or do anything when the bot is busy using that window). You may switch to other tasks and applications as needed, just ensure 1 and 2.
As a proof of concept, watch my latest demo uploaded 2 or 3 days ago here > https://youtu.be/IXflenwJzhQ.
@voidbydefault I am actually running it on a laptop that is not touched and the window always stays maximized and do not get tampered with. It just recently started to happen since yesterday. Before that, it was not having this issue.
@osama3101995 are you using updated code? Maybe watch the video if you didn't and start from scratch. Take a backup of your config.yaml
and setup the whole thing from scratch as shown in video.
EDIT: Let me further investigate this to identify the problem and then a fix. I am unfortunately (or fortunately) unable to produce this error.
@voidbydefault Huh, strange. Is it possible that version of selenium or some difference of a version of a library is causing this issue?
PS: Yes, i just downloaded the updated code. and I will give it a try with the video when free.
Thanks for your help, please update us whenever you find something.
difference of a version
No, version mismatch will prevent the bot from running at all.
I get the same error but only when I set "remote: True" in the config. Similar issue in the previous repo:
Thanks @exshak for pointing it out.
I have made minor changes in the code, hopefully it would fix the issue. Since, I never faced the same error so I cannot confirm from my side. However, requesting all of you (@matthewalampe @osama3101995 @exshak) of you to redownload the code, try, test, and confirm.
EDIT: To keep it simple, change is in linkedineasyapply.py
so you may only download this file instead of the whole thing.
I get the same error but only when I set "remote: True" in the config. Similar issue in the previous repo:
Can anyone test this as well? Set remote: True
to remote: False
in line 6 of config.yaml
.
I should be able to test it tomorrow morning. Remote is set to true for me, so it would make sense if that was causing it
From: taimur @.> Sent: Thursday, August 10, 2023 12:59 PM To: voidbydefault/EasyApplyBot @.> Cc: mal fixmyac.net @.>; Mention @.> Subject: Re: [voidbydefault/EasyApplyBot] Stale Element Error (Issue #13)
I get the same error but only when I set "remote: True" in the config. Similar issue in the previous repo:
Can anyone test this as well? Set remote: True to remote: False in line 6 of config.yaml.
— Reply to this email directly, view it on GitHubhttps://github.com/voidbydefault/EasyApplyBot/issues/13#issuecomment-1673829314, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BADHDDEU2YIQAGSELD5ALIDXUU4RFANCNFSM6AAAAAA3KWU5DQ. You are receiving this because you were mentioned.Message ID: @.***>
I tested this change.
Loops here:
I get the same error but only when I set "remote: True" in the config. Similar issue in the previous repo:
Can anyone test this as well? Set
remote: True
toremote: False
in line 6 ofconfig.yaml
.
I am now running w/ "Remote: False"
Yes, I confirm the application works for, "Remote: False"
When "Remote: True" stale element exception.
Hmm.. any ideas on the fix? I will try and mess with the code later. Unfortunately, I am a coding noob
From: Tyler Maginnis @.> Sent: Thursday, August 10, 2023 1:25 PM To: voidbydefault/EasyApplyBot @.> Cc: mal fixmyac.net @.>; Mention @.> Subject: Re: [voidbydefault/EasyApplyBot] Stale Element Error (Issue #13)
Yes, I confirm the application works for, "Remote: False"
When "Remote: True" stale element exception.
— Reply to this email directly, view it on GitHubhttps://github.com/voidbydefault/EasyApplyBot/issues/13#issuecomment-1673864380, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BADHDDCAPUM5FKQFMS4COG3XUU7TVANCNFSM6AAAAAA3KWU5DQ. You are receiving this because you were mentioned.Message ID: @.***>
Thanks for input @matthewalampe and @tylermaginnis . Keeping it simple, I will think about disabling remote :
for now.
@matthewalampe coding isn't required. Just follow this.
Will that mean it won't apply for any Remote jobs, then?
From: taimur @.> Sent: Thursday, August 10, 2023 1:53 PM To: voidbydefault/EasyApplyBot @.> Cc: mal fixmyac.net @.>; Mention @.> Subject: Re: [voidbydefault/EasyApplyBot] Stale Element Error (Issue #13)
Thanks for input @matthewalampehttps://github.com/matthewalampe and @tylermaginnishttps://github.com/tylermaginnis . Keeping it simple, I will think about disabling remote : for now.
@matthewalampehttps://github.com/matthewalampe coding isn't required. Just follow thishttps://github.com/voidbydefault/EasyApplyBot/issues/13#issuecomment-1673829314.
— Reply to this email directly, view it on GitHubhttps://github.com/voidbydefault/EasyApplyBot/issues/13#issuecomment-1673902967, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BADHDDG3EQERU4AXWOY3DLLXUVC25ANCNFSM6AAAAAA3KWU5DQ. You are receiving this because you were mentioned.Message ID: @.***>
I tried to fix it. Just caused more problems.
I really want to apply to remote jobs so I'm going to try and mess with it tomorrow
From: Tyler Maginnis @.> Sent: Thursday, August 10, 2023 3:01 PM To: voidbydefault/EasyApplyBot @.> Cc: mal fixmyac.net @.>; Mention @.> Subject: Re: [voidbydefault/EasyApplyBot] Stale Element Error (Issue #13)
I tried to fix it. Just caused more problems.
— Reply to this email directly, view it on GitHubhttps://github.com/voidbydefault/EasyApplyBot/issues/13#issuecomment-1673974019, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BADHDDHWNJSNNFB7G4WIVI3XUVK2JANCNFSM6AAAAAA3KWU5DQ. You are receiving this because you were mentioned.Message ID: @.***>
I tried to fix it. Just caused more problems.
I just pushed some code changes, please update your local files using git pull
or update project
(if you are using Git + Pycharm IDE) or otherwise download linkedineasyapply.py
and main.py
for replacing the ones on your drive. remote
as a filter (line 6) is now removed from config.yaml
-- that's one change that you may replicate manually or ignore.
Tested and working for me.
I really want to apply to remote jobs so I'm going to try and mess with it tomorrow
remote
was a filter intended to apply for remote jobs only (COVID-19 days). If not set to True
it will eventually apply for all kinds of job, i.e. on-site, remote, and hybrid.
Ohhh got it! So if I have remote under location, it should still use that. Thanks so much! I will test your new code out later
From: taimur @.> Sent: Thursday, August 10, 2023 3:23 PM To: voidbydefault/EasyApplyBot @.> Cc: mal fixmyac.net @.>; Mention @.> Subject: Re: [voidbydefault/EasyApplyBot] Stale Element Error (Issue #13)
I really want to apply to remote jobs so I'm going to try and mess with it tomorrow
remote was a filter intended to apply for remote jobs only (COVID-19 days). If not set to True it will eventually for all kinds of job, i.e. on-site, remote, and hybrid.
— Reply to this email directly, view it on GitHubhttps://github.com/voidbydefault/EasyApplyBot/issues/13#issuecomment-1674001818, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BADHDDHPPEF4EOCTYRWAZ4LXUVNORANCNFSM6AAAAAA3KWU5DQ. You are receiving this because you were mentioned.Message ID: @.***>
Ohhh got it! So if I have remote under location
You may do so, it's fine as a location
search -- that's how it will look:
config.yaml
bot in action
I think it's working flawlessly now and we can close this thread.
I think I have found the issue. Its with the base_search_url. The easy_apply_url and remote_url query parameters have been updated by LinkedIn it seems. I updated these two and I am not getting the error anymore.
Edit:
easy_apply_url should be "&f_AL=true" rather than "&f_LF=f_AL" remote_url should be "&f_WT=2"
Thank you all for fixes as well.
easy_apply_url should be "&f_AL=true" rather than "&f_LF=f_AL" remote_url should be "&f_WT=2"
Thanks Osama.
My last update to code was to remove remote
filter (see https://github.com/voidbydefault/EasyApplyBot/issues/13#issuecomment-1673999906). LinkedIn also modified this filter for values including hybrid
, on-site
, and remote
. I will take a note of your suggestion in next update.
@osama3101995
I think I have found the issue. Its with the base_search_url. The easy_apply_url and remote_url query parameters have been updated by LinkedIn i
easy_apply_url should be "&f_AL=true" rather than "&f_LF=f_AL" remote_url should be "&f_WT=2"
I have tested your suggestions and pushed after successful testing. Thanks again.
I used the latest code, brand new, and configured as little as possible in the config.yaml (in case something was causing the issue) Still getting the stale element error.. It only applies to one job then stops. Anything I could provide to help troubleshoot?