Browser extension cannot log in (new!)

[GoogleCodeExporter]

While this results in the same outcome as issue 319, it appears to be a very 
different issue, with different symptoms and to which the same workaround does 
not apply.

What steps will reproduce the problem?
1.Install the extension succesfully (No problems)
2.Click the Extension icon and select log in.
3.Click "Allow access"
4.Get redirected to about:blank, and the extension is still not logged in.

What is the expected output? What do you see instead?
The extension should have logged in, it has not.
The OAuth authorization page has a warning on the top: "We are unable to verify 
the name associated with this application because it runs on your computer, as 
opposed to on a website. We recommend you do not allow access unless you trust 
the application". 
Fixing the system time (as is suggested in issue 319) does not help. It's sad 
to notice that the unofficial FoxToPhone extension for Firefox, which uses the 
same service back end, works flawlessly instead.

I am using extension version 2.3.2 on Chrome 31 beta on Windows 7 x64.

Original issue reported on code.google.com by andreazz...@gmail.com on 3 Nov 2013 at 3:12

[GoogleCodeExporter]

I have the same problem.

Original comment by pfuentes...@gmail.com on 17 Nov 2013 at 4:32

[GoogleCodeExporter]

I'm having the same issue with Chrome to Phone extension on the Chrome browser.

Original comment by tao2qu...@gmail.com on 17 Nov 2013 at 6:24

[GoogleCodeExporter]

I'm having the same issue as well.

Original comment by yalina...@google.com on 17 Nov 2013 at 6:25

[GoogleCodeExporter]

Chiming in to also report the problem. Hopefully this will get noticed. I have 
since moved back to Firefox because FoxToPhone works.

I have a similar problem with the Chrome to Mobile extension albeit, CtM first 
goes to google.com/robot.txt first before redirecting to about:blank.

This happens on both Windwos 8.1 and OSX 10.9 with Chrome version 31+.

Original comment by samuel.h...@gmail.com on 19 Nov 2013 at 12:41

[GoogleCodeExporter]

Sorry about that. I just pushed a new Chrome extension (v2.3.3) that fixes 
this. Thanks for the bug reports.

Original comment by burke.da...@gmail.com on 19 Nov 2013 at 4:58

• Changed state: Fixed

[GoogleCodeExporter]

I can confirm that the extension is now fixed and fully functional for me. 
Thank you very much.

Original comment by andreazz...@gmail.com on 19 Nov 2013 at 6:26

[GoogleCodeExporter]

I am having the same problem and today is January 28 2014. Do I need to do 
something to get this to work?

Liz

Original comment by lhm1...@gmail.com on 29 Jan 2014 at 2:58

[GoogleCodeExporter]

I am facing a similar issue on a test app I am developing. A google search for 
the error took me to this page. I would be nice if you can give suggestions on 
how the OAuth error can be fixed.

Original comment by sreekuma...@gmail.com on 22 Oct 2014 at 7:49