Repository navigation
Replies: 1 comment
|
The missing answers.json file is not the actual issue here. It's a normal warning that shows up on the first run of the bot, as it only creates this file after filling out the first application form. The real problem is at the bottom of your log, where Selenium is unable to find the jobs list on LinkedIn's results page. This error typically occurs when the search returns no results for your specified filters. To troubleshoot this, you can try a few things: First, check your position term in config.yaml. LinkedIn matches it literally, so try using a broader term to see if that returns any results. You can also try clearing the date and experience level filters if you've set them. It's also a good idea to log into LinkedIn manually using the same Chrome profile and confirm that a search for the same term shows results. If the results show up manually but the bot still fails, it's likely that your version is outdated. LinkedIn has changed their DOM several times, and older versions of the bot may have stale XPaths. In this case, try pulling the latest version and retrying. Once the bot is able to land on a results page with actual job listings, the exception and the empty output folder should both go away. |
Uh oh!
There was an error while loading. Please reload this page.
Any ideas as to why?

All reactions