Chrome To Phone Requiring Multiple Sign-Ins

[GoogleCodeExporter]

Please answer the questions about build version and network, will save
developers a lot of time !

What steps will reproduce the problem?
1.Start Chrome session on Kubuntu 10.10
2.Sign into Google account.
3.Click chrome to phone icon, and you are prompted to sign in again.

What is the expected output? What do you see instead?
Once signed into to Google account I should not need to sign in to use 
ChrometoPhone. 

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

VZW. Latest 2.2.1 OTA update for Droid X.

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

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

Yes.

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

N/A

Please provide any additional information below.

Original issue reported on code.google.com by patrickb...@gmail.com on 15 Dec 2010 at 1:39

[GoogleCodeExporter]

I'm also having this problem.  I'm signed in to the same account in Chrome and 
on my T-Moblie G2 Android 2.2 phone.  I click the Chrome to Phone button, it 
prompts me to sign in.  I sign in and try the Chrome to Phone button again.  It 
prompts me to sign in again.  This keeps going until I just give up.

Original comment by ted.volt...@gmail.com on 30 Mar 2011 at 5:10

[GoogleCodeExporter]

I find that the constant need to re-authenticate greatly reduces the 
functionality of Chrome to Phone.  I have twice tried to send a link I needed 
from my laptop as I was leaving, only to never receive it.  When I return and 
open my laptop back up, I see a tab asking me to authorize the app for the 
thousandth time.

As this appears to be by design, it is not unique to a single OS.  I can 
confirm that this is an issue in Ubuntu 10.10, Windows 7 Starter, Windows 7 
Home Premium, Windows Vista, Windows XP Home and Windows XP Pro.

Original comment by mattwolf...@gmail.com on 30 Mar 2011 at 6:43

[GoogleCodeExporter]

I found the solution to this problem while troubleshooting a similar problem 
with the Google Tasks Chrome extension 
(https://chrome.google.com/webstore/detail/dmglolhoplikcoamfgjgammjbgchgjdd).

The problem is with the extension being unable to read 3rd party cookies.  In 
chrome://flags I had "block 3rd party cookies from being read" enabled.  I 
guess even though these are Google extensions, they're still treated as 3rd 
parties and are blocked from reading your Google cookie.  You can still keep 
3rd party cookies from being set under Content Settings, but you need to 
disable the option in Flags.

I hope this helps, and I hope that in the future, Google extensions can be 
treated as 1st parties.

Original comment by ted.volt...@gmail.com on 13 May 2011 at 8:43