Closed jawilson closed 6 years ago
Hi @jawilson . I am on vacation until the 24th so I will not be able to look into this until then. If you have any python skills what you could do is edit that last exception to print the response received so we can see what goes on.
I have the same issue, see attachment. reponse.txt
Please read #27 and make sure you have enabled push 2fa.I will look into this after the 24th.
Currenlty 2fa is disabled for the specific account. When I open the response in a browser, I get this:
That means that your phone is not set up for your account. Seems like you have 2fa enabled but not a mobile connected, or something.
I have now fixed it by adding the account to my phone and using push prompt.
I do have to make a remark, if the device is unknown I need to chose a number, when you select the wrong number the device is blocked.
That is google process I am afraid and has nothing to do with this library. I am glad that things now work for you!
@jawilson could it be that your issue is the same?
I'm actually having the same issue and when dumping out the response.text the form has a captcha response in it. I don't get that on any other browser. It's not showing up in the device activity either.
Are you sure you are using the latest version of the library?
I'm specifically using this within homeassistant but moved on to testing lower level with the cookie retrieval since it doesn't seem to be working in homeassistant. It's a virtualenv that has 2.0.11 installed as part of homeassistant:
homeassistant) homeassistant@homeautomation:~/.homeassistant$ pip3.6 show locationsharinglib Name: locationsharinglib Version: 2.0.11
I'm also getting the captcha, I checked out from GitHub to be sure.
I will have a look at the captcha prompt issue after I am back from vacation after the 24th, so please be patient.
So after waiting a few days and trying again I finally did get a sign-in alert from google to be able to approve and things look good now. Unsure why it was not showing up before but all works well now. Thanks.
Closing this as it seems that it is a missing google account setting from the user's side.
I'm receiving the following: