login failing

[GoogleCodeExporter]

What steps will reproduce the problem?
1. create an app password
2. use the app password into the pidgin mightytext settings
3. enable the mightytext account in pidgin

What is the expected output? What do you see instead?

I get "Authentication failed"

What version of the product are you using? On what operating system?

I'm using the following SVN revision: 
http://pidgin-mightytext.googlecode.com/svn/trunk@18 
e81797ad-9f93-8b55-6e24-e607140ff0e9

Compiled on Debian Jessie using the following makefile: 
https://github.com/tubaman/pidgin-mightytext/blob/717afd634e423bc1142a227afbd51c
f92722bca0/Makefile

Original issue reported on code.google.com by r...@keyingredient.com on 1 Jun 2015 at 7:19

[GoogleCodeExporter]

I'm having the same issue today.  Never had it before.

I'm using Version 1.0.

Original comment by eddi...@gmail.com on 2 Jun 2015 at 1:09

[GoogleCodeExporter]

Unfortunately Google removed the API I was using to authenticate
https://developers.google.com/accounts/docs/AuthForInstalledApps

I'll start working on the newer auth :)

Original comment by eionrobb on 2 Jun 2015 at 2:22

• Changed state: Accepted

[GoogleCodeExporter]

Same issue here, definitely love the plugin and hoping to see a fix soon :)

Original comment by BryanKru...@gmail.com on 2 Jun 2015 at 3:09

[GoogleCodeExporter]

I started having this issue a few days ago as well, but only on one of my 
machines. The mightytext plugin still works on my 2nd machine strangely. 

Original comment by nflow...@gmail.com on 6 Jun 2015 at 5:34

[GoogleCodeExporter]

It's the same for me as #4. My work PC (Win7 Enterprise 64 bit, Pidgin 2.10.9) 
will not longer connect, but my home PC (Vista Ultimate 64 bit, possibly older 
Pidgin) will connect just fine.

Original comment by Illithid...@gmail.com on 8 Jun 2015 at 12:36

[GoogleCodeExporter]

Well, I guess my authentication expired on my one PC where it was still 
working, now neither works. 

Thanks for working on the newer auth eionrobb! 

Original comment by nflow...@gmail.com on 9 Jun 2015 at 12:30

[GoogleCodeExporter]

the plugin seems to be working again this afternoon.
Not sure if it matters, but I have a browser session open to gmail and I"m 
logged in.  I also have a browser session open to the mightytext webpage.

Thought you should know.

Original comment by eddi...@gmail.com on 12 Jun 2015 at 5:01

[GoogleCodeExporter]

That's very strange.  Just as @eddiem9 says it started working without any 
changes.  I just tried to re-enable and it appears to be working again.

I'll still keep working on updating the auth just in case they turn off the old 
ClientLogin again

Original comment by eionrobb on 12 Jun 2015 at 9:05

[GoogleCodeExporter]

I confirm that today plugin start working without any changes. 

Original comment by sobo...@gmail.com on 12 Jun 2015 at 10:21

[GoogleCodeExporter]

I can also confirm. It's working again. I didn't do anything except re-enable 
it in Pidgin 2.10.9.

Original comment by Illithid...@gmail.com on 18 Jun 2015 at 8:22

[GoogleCodeExporter]

It's still broken for me

Original comment by r...@keyingredient.com on 24 Jun 2015 at 3:39

[GoogleCodeExporter]

It had also started working again for me along with #7-10, but now it's broken 
again like with #11. 

Original comment by nflow...@gmail.com on 27 Jun 2015 at 5:41

[GoogleCodeExporter]

Yup, it's broken again.

Original comment by kevinb...@gmail.com on 27 Jun 2015 at 8:14

[GoogleCodeExporter]

In the Pidgin debug log I can see it gets a 404 response from Google during the 
login attempt which results in the failure.  All of the output looks normal 
until the 404 (as far as I can tell):

...
(07:55:01) certificate: Successfully verified certificate for www.google.com
(07:55:01) util: request constructed
(07:55:01) util: Response headers: 'HTTP/1.0 404 Not Found

Content-Type: text/plain

X-Frame-Options: DENY

Cache-control: no-cache, no-store

Pragma: no-cache

Expires: Mon, 01-Jan-1990 00:00:00 GMT

Date: Mon, 29 Jun 2015 14:55:01 GMT

X-Content-Type-Options: nosniff

X-XSS-Protection: 1; mode=block

Content-Length: 65

Server: GSE

Alternate-Protocol: 443:quic,p=1

'
(07:55:01) util: parsed 65
(07:55:01) connection: Connection error on 0B6A99A8 (reason: 2 description: 
Authentication failed)

Original comment by phil.sch...@gmail.com on 29 Jun 2015 at 3:00

[GoogleCodeExporter]

Like #12....not working here, either.  Mine spontaneously started working on 
June 11th, then 2 days ago it cut out with "Auth failed" messages again and 
won't connect.  

Thank you for taking time to work on this!  :)

Original comment by jmstoeh...@gmail.com on 2 Jul 2015 at 2:10

[GoogleCodeExporter]

So I've been trying very unsuccessfully to get the auth going, but I just 
wanted some feedback from you users:

Pushbullet has recently announced support for forwarding SMS, and they have a 
real API that isn't all hacky like the MightyText one.  Would you be in favour 
of me ditching this plugin to start a Pushbullet plugin instead?

Original comment by eionrobb on 18 Jul 2015 at 6:15

[GoogleCodeExporter]

Definitely. Please do.

Original comment by bogdan.a...@gmail.com on 18 Jul 2015 at 7:12

[GoogleCodeExporter]

Yes please! Thank you! 

Original comment by nflow...@gmail.com on 18 Jul 2015 at 3:13

[GoogleCodeExporter]

MightyText's webapp has gotten pretty "bloated," if you will, anyway. And if 
you can't get MightyText working with Pidgin easily anyway, put me on the list 
of "yeppers" to Pushbullet.

Original comment by kevinb...@gmail.com on 18 Jul 2015 at 4:02

[GoogleCodeExporter]

I would have preferred MightyText (prefer their web UI) but PushBullet would 
work just as well. Any work you put into this is greatly appreciated!

Original comment by Eric.W.F...@gmail.com on 20 Jul 2015 at 2:46

[GoogleCodeExporter]

I like Mighty-text's ability to send texts from my tablet and I don't really 
find the web interface that bloated -- but maybe that's just my machine's 
specs? I'd prefer this just be resolved, but ultimately I need the ability to 
text from Pidgin, so whatever course that requires.

Original comment by ille.pug...@gmail.com on 20 Jul 2015 at 4:52

[GoogleCodeExporter]

Go for it!  I had actually never heard of PushBullet until you mentioned it, 
but I definitely prefer it to MightyText.  Maybe a bit less-featured than MT 
(no tablet texting yet), but definitely prettier and cleaner.  Thank you again 
for all the work -we appreciate it!

Original comment by jmstoeh...@gmail.com on 20 Jul 2015 at 6:05

[GoogleCodeExporter]

I vote for PushBullet integration.

Original comment by david.ch...@gmail.com on 22 Jul 2015 at 4:50

[GoogleCodeExporter]

#20 and #21, even if you prefer MightyText, you can still use their web UI and 
tablet app and only use Pushbullet for Pidgin. I've been using both and haven't 
seen them interfere with each other. 

Original comment by nflow...@gmail.com on 22 Jul 2015 at 5:12