Sending "Chrome to Phone" link or text to Nexus S (ICS) causes crash.

[GoogleCodeExporter]

What steps will reproduce the problem?

1. Highlight text in Chrome on Windows 7 32-bit (16.0.912.77 m) 
2. Right click highlighted-text and select "Chrome to Phone"
3. App (2.2.0) crashes on phone (ICS IML74K)  displaying message " 
Unfortunately, Chrome to Phone has stopped"

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

Have tried via WiFi and 3G.  No firewall present.

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

Yes, yes.

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

Yes.

Additional info:

Only thing off the top of my mind that I've changed is setting up google 
services for double-authentication, but I have authenticated the services on 
the phone through "https://www.google.com/accounts/IssuedAuthSubTokens"

have tried rebooting phone, rebooting PC, uninstalling and re-installing app 
and chrome extension.  Same problem.

Original issue reported on code.google.com by ryan.how...@gmail.com on 25 Jan 2012 at 8:12

[GoogleCodeExporter]

I second this

Original comment by damienre...@gmail.com on 26 Jan 2012 at 8:28

[GoogleCodeExporter]

I saw this too on Nexus S ICS... today's updtae seems to have fixed teh crash 
(it was an NPE, I sent the crash report in).

But now we're back to that old bug where you select text in a page and pick 
"Chrome to Phone" from the content menu and it sends the page URL instead of 
the selected text  

Original comment by margaret...@gmail.com on 1 Feb 2012 at 8:00

[GoogleCodeExporter]

2.3.0 changes the behavior to always send the page URL in addition to the 
selected text. Two reasons for the change:
1. Many people were confused by the feature (they'd accidentally select text 
and no notice the notification that said the clipboard was copied).
2. Some websites automatically select text in the Web page without user 
involvement.

Original comment by burke.da...@gmail.com on 2 Feb 2012 at 12:41

• Changed state: Fixed

[GoogleCodeExporter]

In that case make it optional to send text only! We neeeeeed it! (A) At least, 
I do.

Original comment by JhJoos...@gmail.com on 23 Mar 2012 at 2:46

[GoogleCodeExporter]

Please bring this feature back as an option, this was the best feature, and 
something I  demonstrated as an advantage over iPhone. Now I have to look for 
alternatives.

Original comment by GMike...@gmail.com on 28 Mar 2012 at 12:33

[GoogleCodeExporter]

For anyone still interested, I made a patch to be able to send custom text to 
the phone (see http://code.google.com/p/chrometophone/issues/detail?id=162), 
doesn't seem to be picked up though. I am able to create/host a custom 
apk/chrome extension, you would have to allow custom apk's for your android 
device in that case though.

Original comment by dfa...@gmail.com on 19 Apr 2012 at 6:29

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

OMG< please bring back the send text feature back!!! I used this so much, since 
I hate typing on my phone. The reasons for change seem also quite strange to 
me: I think many more people are confused now and I've never encoutered issue 
#2...

Please bring it back... Or make it a setting...

Original comment by verh...@gmail.com on 3 Apr 2013 at 11:06

[GoogleCodeExporter]

The description on the Play store says "Google Chrome to Phone lets you easily 
share links, maps, and currently selected phone numbers and text between your 
computer running Chrome and your phone.". It sounds like this latest update is 
contrary to that --- so you either need to update the description on the Play 
store or (ideally) bring back the old functionality...

Original comment by t...@tomkerswill.co.uk on 6 Jun 2013 at 4:37