fredyang / chrometophone

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

not working with "gmail multiple sign-in" feature turned on? on Chrome 6.0.472.62 #219

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
Please answer the questions about build version and network, will save
developers a lot of time !

What steps will reproduce the problem?
1. seems to have stopped working after gmail multiple sign-in is enabled
2.
3.

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

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

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

doesn't work for either wifi or mobile data

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.

Original issue reported on code.google.com by kevhuan...@gmail.com on 22 Sep 2010 at 5:13

GoogleCodeExporter commented 9 years ago
I'm having this issue too.  Here are some more details:

C2P worked fine on my phone before I enabled multiple sign-in on my Google 
account.  Now when I click the C2P button in my browser, I am prompted to sign 
in to C2P.  When I click the "sign in" link I am taken to a page to select my 
Google account.  This page is formatted in a very plain manner, unlike most 
other Google properties.  I select my (main) Google account, and then I am 
taken to a page which contains an error message.  I've attached two screenshots 
here.

The "report your problem" link on this page redirects to 
http://code.google.com/appengine/community.html, which is no help for reporting 
problems - a search for "Chrome to Phone" on that site returns no hits.

Phone build number: FRG83
Gmail and Talk apps work fine, as expected (yes, I can see new messages and 
chats).
The problem is on the browser side, so I have not seen any changes with using 
wifi or mobile data.

Original comment by kell...@gmail.com on 3 Mar 2011 at 8:08

Attachments:

GoogleCodeExporter commented 9 years ago
Sorry; I should have given more specifics about my Chrome browser, too: current 
version  is 10.0.648.126 beta, although a new version seems to be installing as 
we speak.

I would reclassify this as a high priority bug because it makes the extension 
completely unusable.

Original comment by kell...@gmail.com on 3 Mar 2011 at 8:10

GoogleCodeExporter commented 9 years ago
I'm having the same issue using Google Chrome 10.0.648.127.

Text of error message is:
Error: Server Error

The server encountered an error and could not complete your request.
If the problem persists, please report your problem and mention this error 
message and the query that caused it.

Original comment by sheld...@rsscooters.com on 9 Mar 2011 at 2:33

GoogleCodeExporter commented 9 years ago
Multiple accounts work fine for me with Firefox and FoxToPhone

Original comment by aml...@gmail.com on 9 Mar 2011 at 3:01

GoogleCodeExporter commented 9 years ago
I am also seeing this error in Chrome 10.0.648.127

Original comment by diano...@3dgo.net on 10 Mar 2011 at 5:03

GoogleCodeExporter commented 9 years ago
Identical issue, Chrome 10.0.648.134, OS X 10.6.6

Original comment by randy.le...@gmail.com on 17 Mar 2011 at 9:03

GoogleCodeExporter commented 9 years ago
Identical issue. Chrome 11.0.696.14, OSX 10.6.6 and Windows 7 (x64).

Original comment by acco.gra...@gmail.com on 20 Mar 2011 at 9:32

GoogleCodeExporter commented 9 years ago
I have the same problem with 3 Google accounts. 
10.0.648.151

Original comment by jshell...@gmail.com on 22 Mar 2011 at 5:59

GoogleCodeExporter commented 9 years ago
Same problem. Using wifi. Chrome 10.0.648.151. GT-I5700 2.2.1 Kernel 2.6.29.6 
CyanogemMod-6.1.1

Original comment by negr...@gmail.com on 23 Mar 2011 at 6:22

GoogleCodeExporter commented 9 years ago
Seems to be fixed now.

Chrome 12.0.712.0

Original comment by acco.gra...@gmail.com on 31 Mar 2011 at 1:59