Links sent with "Silent Sending" option always go to the browser identified by "Chrome"

[GoogleCodeExporter]

Account is/is not set up and chosen: Is set up and chosen
Android version: 2.2
Android device has/has not been rooted/modified: Not rooted (Stock Rom)
Android device: HTC Vision (T-Mobile G2)
Carrier: T-Mobile
Country: USA
Version of android2cloud Android app: 2.0.1
The server I'm using: my own, with the latest source
The Google Account name that I logged in with: my own account
What I am doing, step-by-step: set up app to use my server, turn on silent 
sending, send a link to the cloud
What I expect to see: The link go to a browser/computer of my choosing
What I see: The link only goes to the browser with the identifier "Chrome"

I suggest that the app either remember the last identifier used for sending 
manually, or preferably have the identifier as a part of the account setting 
and allow for more than one identifier

Original issue reported on code.google.com by dave...@gmail.com on 7 Jan 2011 at 12:31

[GoogleCodeExporter]

Have you sent a link to a non-Chrome browser yet? The app should send it to the 
last browser you sent to.

Original comment by foran.pa...@gmail.com on 7 Jan 2011 at 12:50

• Changed state: Investigating

[GoogleCodeExporter]

I have been using chromium 10.0.628.0 for all tests, but when I change the 
identifier in the extension options, I am no longer able to send to the browser 
using the silent sending option, the app defaults to sending to 
[username]@gmail.com/Chrome as shown in the logs on appengine.

I have sent a link to the browser manually using an alternate identifier 
(Chrome2 for this test) and then immediately sent a link from the browser using 
the share menu, and it sent to identifier 'Chrome'

Original comment by dave...@gmail.com on 7 Jan 2011 at 3:07

[GoogleCodeExporter]

Thanks for the info. I'll look into it, and try to issue a patch shortly.

Original comment by foran.pa...@gmail.com on 7 Jan 2011 at 9:31

• Changed state: Accepted

[GoogleCodeExporter]

This is in beta testing at the moment. If nothing goes wrong, it will be rolled 
out to everyone on Thursday.

Sorry for the delay.

Original comment by foran.pa...@gmail.com on 18 Apr 2011 at 11:02

• Changed state: InBeta

[GoogleCodeExporter]

This was fixed in version 2.0.5.1

Original comment by foran.pa...@gmail.com on 6 Aug 2011 at 6:19

• Changed state: Fixed