Country code Canada (+1) not found! Make sure it is exact. Could not input phone number.

[logix727]

Applying to the job.... Country code Canada (+1) not found! Make sure it is exact. Could not input phone number. Country code Canada (+1) not found! Make sure it is exact.

[logix727]

gets stuick when trying to start application

[Briwhee]

This is the same issue with Issue #2 that I posted.

[madingess]

I am not able to reproduce this issue, even when I leave that line in the configuration file unchanged.

Since there have been a number of issues arise related to varying package and python versions, I added a virtual environment to the project tracking. Will you please try again using the updated Setup & Startup section of the README to see if this issue persists?

[logix727]

Will re check when home tomorrow

On Wed, Dec 7, 2022, 9:11 PM Michael Dingess @.***> wrote:

I am not able to reproduce this issue, even when I leave that line in the configuration file https://github.com/madingess/EasyApplyBot/blob/master/config.yaml#L150 unchanged.

Since there have been a number of issues arise related to varying package and python versions, I added a virtual environment to the project tracking. Will you please try again using the updated Setup & Startup section of the README https://github.com/madingess/EasyApplyBot/blob/master/README.md#setup--startup to see if this issue persists?

— Reply to this email directly, view it on GitHub https://github.com/madingess/EasyApplyBot/issues/4#issuecomment-1341878834, or unsubscribe https://github.com/notifications/unsubscribe-auth/AEPXCRSADVB35XBDWBGKERTWME7WRANCNFSM6AAAAAASXC2ZAY . You are receiving this because you authored the thread.Message ID: @.***>

[logix727]

t-master$ source venv/bin/activate bash: venv/bin/activate: No such file or directory

[madingess]

To run the bot, open the command line in the cloned repository directory. Activate the virtual environment and start the bot using these commands:

source venv/bin/activate
python3 main.py

You need to change your directory to the folder where you store the repository.

[logix727]

sorry didnt have cofffe yet m8 this is in teh virtual enviroment what python version are you using perchance?

not input phone number. Country code United States (+1) not found! Make sure it is exact. Could not input phone number. Country code United States (+1) not found! Make sure it is exact. Could not input phone number. Country code United States (+1) not found! Make sure it is exact. Could not input phone number.

and with canada / the default config ready applied to the job! Applying to the job.... Country code Canada (+1) not found! Make sure it is exact. Could not input phone number. Country code Canada (+1) not found! Make sure it is exact. Could not input phone number. Country code Canada (+1) not found! Make sure it is exact. Could not input phone number.

[madingess]

If I recall correctly the virtual environment uses 3.6.8

[madingess]

If you try changing the phone number configuration line to Phone Country Code: United States (+1) does it work?

[madingess]

If you are still experiencing issues after trying that, you can try commenting out line 721 of linkedineasyapply.py (Add the pound sign #)

->

                        #self.select_dropdown(country_code_picker, self.personal_info['Phone Country Code'])

I don't want to remove the functionality from the project entirely unless the problem is more widespread and more reproducible.

[madingess]

Also, this exception should not halt functionality. It should leave selected whatever country code was previously selected, then continue to enter the remaining information. Does it stop the application entirely when you see this output?

[logix727]

correct it breaks it as it cannot add the phone number next let me try with the comment

[logix727]

Country code Canada (+1) not found! Make sure it is exact. Could not input phone number. with line 721 commented. im gonna purge my python install and reinstall to see if that helps

[logix727]

[madingess]

That is a new presentation, but likely for the same error. Will you please share a screenshot with the following: right-click the phone number input box and choose inspect. Please include the class attribute in the screenshot. An example:

If you are indeed in Canada, you may be getting served a linkedin page which uses different values for the class attributes. The screenshot should help. Also, is your URL ca.linkedin.com?

[logix727]

sure can not in canada in us dont mind the canada default

<input class=" artdeco-text-input--input" id="single-line-text-form-component-formElement-urn-li-jobs-applyformcommon-easyApplyFormElement-3391844020-76853307-phoneNumber-nationalNumber" required="" aria-describedby="single-line-text-form-component-formElement-urn-li-jobs-applyformcommon-easyApplyFormElement-3391844020-76853307-phoneNumber-nationalNumber-error" type="text">

[madingess]

Thank you. Oddly the class attribute in your page is different from mine. I am also in the US.

That said, this may be enough to change the way it looks for these fields in a way which works for both of us. I may need this same information for other fields, but let's see what happens if I can fix the phone number input first.

[logix727]

cool let me know what i can do to help

On Thu, Dec 8, 2022 at 12:40 PM Michael Dingess @.***> wrote:

Thank you. Oddly the class attribute in your page is different from mine. I am also in the US.

That said, this may be enough to change the way it looks for these fields in a way which works for both of us. I made need this same information for other fields, but let's see what happens if I can fix the phone number input first.

— Reply to this email directly, view it on GitHub https://github.com/madingess/EasyApplyBot/issues/4#issuecomment-1343072383, or unsubscribe https://github.com/notifications/unsubscribe-auth/AEPXCRRDWNQ7NSJEMKNBFZTWMIMRNANCNFSM6AAAAAASXC2ZAY . You are receiving this because you authored the thread.Message ID: @.***>

[madingess]

Luckily the day after this conversion occurred it started serving me the new webpage. I've now updated it to work with the new linkedin webpage and hopefully be more robust so future changes aren't necessarily breaking.

Please try it again and let me know.

[madingess]

Please reopen if the issue persists.