search

gavinzheng / chrometophone

Automatically exported from code.google.com/p/chrometophone
0 stars 0 forks source link

Not working wit 2-step verification #287

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Configure you Google Apps account for 2-step verification
2. Try and sign in to Chrome to Phone.

What is the expected output? What do you see instead?
https://chrometophone.appspot.com/_ah/conflogin
Error: Server Error
The server encountered an error and could not complete your request.

What version of the android, in Settings -> About phone -> Build number (ex. 
FRFxx ) ? If less than FRF50 - see the FAQ.
FROYO.BOJPB

Is the phone using WiFi or mobile network when problem occurs ? If Wifi,are you 
behind a firewall that blocks outgoing connections ?
Using Wi-Fi, no firewall

Can you open "Gmail" application ? Do you see new messages without hitting 
'refresh' ?
Yes

Can you open "Talk" application ? Do you see incoming chats ?
Yes

Please provide any additional information below.
Google Chrome to Phone Extension 2.1.3
Google Chrome 10.0.648.82 beta
Debian Testing

Original issue reported on code.google.com by reu...@honigwachs.de on 6 Mar 2011 at 10:46

GoogleCodeExporter commented 9 years ago 
I have cleared browser cache and sign-in (providing account and verification 
code) worked afterwards.

Original comment by reu...@honigwachs.de on 6 Mar 2011 at 3:32

GoogleCodeExporter commented 9 years ago 
I have the same problem and clearing cache or reinstalling the app does not 
help.

Original comment by KPoc...@gmail.com on 10 Mar 2011 at 7:39

GoogleCodeExporter commented 9 years ago 
I'm getting this same issue, but I don't have two step auth enabled. I *do* 
have multiple account sign in turned on, however.

Original comment by JonEcks...@gmail.com on 10 Mar 2011 at 9:49

GoogleCodeExporter commented 9 years ago 
Same issue, I also have two-factor authentication enabled.

Original comment by da...@allpowerfuldave.com on 4 May 2011 at 1:55

GoogleCodeExporter commented 9 years ago 
Next release will switch the authentication code to OAuth and solve most 
problems. 

Since it's a big change and we need to make sure it'll work with the older 
extensions - it needs some extra testing, not sure when Dave will cut the build.

Original comment by costin on 4 May 2011 at 4:15

GoogleCodeExporter commented 9 years ago 
I just checked out the latest source and tried it unpacked. It worked well.

Original comment by 4braham on 4 May 2011 at 6:29