-
Notifications
You must be signed in to change notification settings - Fork 120
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Running gvoice li returning urllib2.HTTPError: HTTP Error 400: Bad Request #53
Comments
Looks like the |
I used Seems like we're still stuck at the same issue, even after not using |
Which version you using? From this repo the |
Correct. I made sure to delete everything and I downloaded the I used |
Did you perform the DUC (display unlock captcha) on your G account for the purposes of allowing cleartext password login from your previously unseen (to google) IP address? https://accounts.google.com/b/0/displayunlockcaptcha NOTE: this is the biggest thing most people miss because it's so poorly documented because the whole world is moving away from cleartext login for obvious reasons. |
I did try that, I saw that in another Issues thread. I tried it again just now and confirmed that I did not have Multi-factor Authentication on as well. Used |
Can you try opening a browser from the same OS X machine and log into |
Tried it now, I was able to log in. I was already logged in in my current browser session; so I logged out, went to |
OK great so the command |
I should clarify, sorry: I was able to log into the web interface. ’gvoice’ still returns the same error as above. |
Can you try it again with the code from this repo: https://github.com/EspaceNetworks/pygooglevoice |
I've been experiencing the seemingly inevitable problem of trying to only login with pygooglevoice. I've gotten this far, but am now stuck with this error.
After using
pip2.7 install
(my Python 3.6 installs have returned errors with the configparser) and setting up my.gvoice
file, I get the following after runninggvoice li
from terminal in OS X 10.13.4.I've had a hard time parsing the code as to how the URL is built; not sure what to do.
The text was updated successfully, but these errors were encountered: