pygooglevoice
pygooglevoice copied to clipboard
on login see: googlevoice.util.LoginError
when I try and run the sms.py example, it fails with error <googlevoice.util.LoginError>.
could it be that google has changed the login url?
Seems to be working for me. What version of python are you running?
2.7.1. since it's working for you I'll go home and try and get a better idea of what's going on.
I am running into the same problem. It appears to be a problem with cookies not being enabled by the script (in __do_page?).
Same Issue, nothing works, 2.7.1 as well
I also changed a URL and nothing
Same issue. I use two factor auth, and can't log in with either an application specific password of my account password.
Same issue for me.
Is this still being actively developed? I can begin looking into this issue tonight.
The way this package is implemented, I don't it'll ever work with application specific passwords as google does not allow you to use those passwords to login to the web google voice site.
http://www.androidpolice.com/2013/11/04/merging-of-google-voice-and-hangouts-will-result-shutting-down-all-3rd-party-voice-apps-in-may-2014/
It appears that this may not work anymore at all, sadly. The Voice API looks like it has been shut down. The only recommendation I see in the Google developer documents is through Twilio.
https://cloud.google.com/appengine/docs/php/sms/twilio#sending_an_sms
What a shame.
I don't think this uses an API. I think this simulates logging in through the browser and sending a text through the web interface. It's a hack :)
That's 100% accurate. This was a hack to basically simulate login and scrape the web UI specifically because there was no API. I found a long-dead version on googlecode in like 2009 and fixed the existing bugs at the time and put it up here. But since then I think google logins have become so much more complicated and changed that the login stuff is now seriously broken. But I don't think the voice UI has changed significantly, so if you're up to it, feel free to make some PRs. But for now, I'm not actively developing this.
On Feb 6, 2015, at 2:05 PM, Nathan Van Gheem [email protected] wrote:
I don't think this uses an API. I think this simulates logging in through the browser and sending a text through the web interface. It's a hack :)
— Reply to this email directly or view it on GitHub.
Oh, it still works. Just doesn't work with application specific passwords--that was my problem.
So if you have 2-factor auth on the google account you want to interface with, you'll need to do the whole sms auth code thing. Which means, you can't use this library to automate any api level stuff with an application specific generated password.
And the reason it doesn't work with application passwords is a google restraint, not a library one. You simply can't login through the web UI with application passwords.
Whoa, neat! I was unaware. @vangheem, I see what you're saying now. Would it be possible to work with a separate account strictly for your purpose without Two-Factor?
Yes.
I get a LoginError today when I didn't yesterday. Has anything changed?
I can check tonight. Are you using the most recent version from this repository?
Downloaded it yesterday morning, it should be.
Great. I'm travelling right now, so I'm on a lot of different wifi networks. Last night there was a brief period in which logins didn't work on my hotel wifi but did using my phone's service (through the Pythonista iOS app). Now it doesn't work either through my phone or on the airport's wifi, nor from a computer in my house that I access through SSH. (It might just be that working or not just happened to coincide with my switching of wifi networks)
Solved! The issue was in the fact that I was signing in while traveling. The fact that I'm in Houston instead of NY was flagged as "suspicious activity" and therefore as soon as I logged in graphically I was prompted to confirm by entering what city I normally logged in from. This was also likely the difference between hotel wifi and my phone.