Unable to locate element: //input[@type="password"]

[tillmann123456]

Hi Samapriya,
thanks a lot for this tool, it looks very helpful. Unfortunately, I can't get the "geeup upload" tool to work. I have run the geeup init command without a problem.
When I run the "upload" command and type in my passowrd, it says "Message: Unable to locate element: //input[@type="password"]. Failed to setup Selenium profile"

When I run the "selsetup" command, a stackauth window opens, but then it says my browser (Firefox) is potentially insecure. I tried changing the standard browser to Chrome, but the stackauth window still opens in Firefox.

Great if you can help me with this!

Tillmann

[samapriya]

Can you create a virtual environment and do a fresh install of geeup v 0.4.5? I just released an update though it should not impact your issue and I was able to run geeup selsetup at my end . Also let me know the python version you are running

[tillmann123456]

Thanks, yes, I installed geeup v0.4.5 in a virtual environment and can run geeup init, but the issue with geeup selsetup persists. I'm running python 3.7.9

[samapriya]

The only next steps I can think of is

• Check that your account does not use duo factor auth since this is not designed for that
• Check that less secure apps are enabled on your google account
• Last but not least try with an alternate account if you have one to test it out, since I am unable to recreate this for my account

[kevinpdavies]

Hi Samapriya - I am having the exact same problem (I checked your first two points above). I noted that geebam also appears to have a similar issue with selenium. Perhaps Google is blocking?

[samapriya]

Unfortunately yes, it seems this is working for a few google accounts and for accounts it simply does not. You are right, google has changed it's policy on embedded and automated browser. For users who have allowed less secure apps it usually works but remains blocked for some accounts. There is some discussion on this here and here is the related blog. I am open to anyone who has a PR that might help fix this but in the mean time I am keeping this issue open

[samapriya]

A related fix is applied to v0.4.6, you can now use cookies to ingest instead of selenium. You can read the docs here
https://samapriya.github.io/geeup/projects/cookies_setup/

Hope this helps, and closing this issue for now but feel free to test and reopen issues as needed.

[SdeRodaHusman]

Dear all,

First of all @samapriya, thanks for this great tool, I expect it will really help me during my research and can't wait to use it.

However, at the moment I am also stuck with this issue ("Message: Unable to locate element: //input[@type="password"]) when trying "geeup selsetup" and "geeup upload ... etc". I also have this issue after updating to version 0.4.6, and also when trying different accounts.

I was wondering if any of you (@tillmann123456 or @kevinpdavies) already got it working? If so, it would be great if you could share some tips.

Thanks in advance :)
Sophie

[samapriya]

Hi @SdeRodaHusman
Since the selenium setup work adhoc with some accounts, might I recommend using the cookies setup method here. You can find the readme website here which I think is easier to navigate
https://samapriya.github.io/geeup

To set up cookies use this
https://samapriya.github.io/geeup/projects/cookies_setup/

and then using the method cookies during image upload as in the example here
https://samapriya.github.io/geeup/projects/image_upload/

This method works for all accounts even with those that have 2-factor auth and/or are Single Sign-on accounts like university accounts. Hope this helps

Sam

[SdeRodaHusman]

Hi @samapriya,

Thank you so much! It is working now, amazing :)
Version 0.4.6 did not allow me to use the cookies setup tool, I think because I am working on Linux, and these cookie-strings were not recognised? Thanks to the changes in 0.4.7., it is working now.

Once again, thanks for the help & the great tool!

All the best,
Sophie

PS. I noticed a minor typo in the explanation on Cookies Setup at PyPI: cookieS_setup, instead of cookie_setup.

[samapriya]

Thanks @SdeRodaHusman for testing it out and for the typo catch will correct it in the next release :) Glad it works