Links sent to multiple accounts(devices) even though it is signed in as single account #51

New Issue

fergalmoran · 2025-08-09T16:56:01Z

fergalmoran commented

2025-08-09 16:56:01 +00:00

Originally created by @GoogleCodeExporter on 1/3/2016

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

What steps will reproduce the problem?
1. Add Chrome to Phone to android phones (S3 & Galaxy Nexus)
2. Each phone has their own single Google (AccountA and AccountB) account that 
is not related.
3. Sign in to Chrome's Chrome to Phone using AccountA. (sending links works as 
expected and only goes to the phone with AccountA)
4. Exchange SIM on the phones
5. Remove Google account on the phones
6. Linked Google accounts back but exchanged. So AccountA goes to the other 
phone and AccountB goes to the phone that AccountA was linked in.
7. Re-install Chrome to Phone app on phones.
8. Send Link via browser.
9. Link goes to both phones. (Unexpected)


What is the expected output? What do you see instead?
Chrome-To-Phone links should only go to the Google account the Browser is 
linked to.  Instead it goes to multiple phones that the Google account "has 
been" with.

What version of the android, in Settings -> About phone -> Build number (
ex. FRFxx ) ? If less than FRF50 - see the FAQ.
Both phones are on 4.1.1 S3 is on JRO03L and G-Nexus is on JRO03C

Is the phone using WiFi or mobile network when problem occurs ? If Wifi,
are you behind a firewall that blocks outgoing connections ?
Tested on and off home WiFi (no firewall).

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


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



Please provide any additional information below.

Original issue reported on code.google.com by hyperat...@gmail.com on 23 Mar 2013 at 7:57

*Originally created by @GoogleCodeExporter on 1/3/2016* ``` Please answer the questions about build version and network, will save developers a lot of time ! What steps will reproduce the problem? 1. Add Chrome to Phone to android phones (S3 & Galaxy Nexus) 2. Each phone has their own single Google (AccountA and AccountB) account that is not related. 3. Sign in to Chrome's Chrome to Phone using AccountA. (sending links works as expected and only goes to the phone with AccountA) 4. Exchange SIM on the phones 5. Remove Google account on the phones 6. Linked Google accounts back but exchanged. So AccountA goes to the other phone and AccountB goes to the phone that AccountA was linked in. 7. Re-install Chrome to Phone app on phones. 8. Send Link via browser. 9. Link goes to both phones. (Unexpected) What is the expected output? What do you see instead? Chrome-To-Phone links should only go to the Google account the Browser is linked to. Instead it goes to multiple phones that the Google account "has been" with. What version of the android, in Settings -> About phone -> Build number ( ex. FRFxx ) ? If less than FRF50 - see the FAQ. Both phones are on 4.1.1 S3 is on JRO03L and G-Nexus is on JRO03C Is the phone using WiFi or mobile network when problem occurs ? If Wifi, are you behind a firewall that blocks outgoing connections ? Tested on and off home WiFi (no firewall). Can you open "Gmail" application ? Do you see new messages without hitting 'refresh' ? Yes, on both Can you open "Talk" application ? Do you see incoming chats ? Yes, on both Please provide any additional information below. ``` Original issue reported on code.google.com by `hyperat...@gmail.com` on 23 Mar 2013 at 7:57

Sign in to join this conversation.

No Label auto-migrated auto-migrated auto-migrated auto-migrated auto-migrated auto-migrated auto-migrated auto-migrated auto-migrated auto-migrated auto-migrated auto-migrated auto-migrated auto-migrated auto-migrated auto-migrated auto-migrated auto-migrated auto-migrated auto-migrated auto-migrated auto-migrated auto-migrated auto-migrated auto-migrated auto-migrated auto-migrated auto-migrated auto-migrated auto-migrated auto-migrated auto-migrated auto-migrated auto-migrated auto-migrated auto-migrated auto-migrated auto-migrated auto-migrated auto-migrated auto-migrated auto-migrated auto-migrated auto-migrated auto-migrated auto-migrated Priority-Medium Priority-Medium Priority-Medium Priority-Medium Priority-Medium Priority-Medium Priority-Medium Priority-Medium Priority-Medium Priority-Medium Priority-Medium Priority-Medium Priority-Medium Priority-Medium Priority-Medium Priority-Medium Priority-Medium Priority-Medium Priority-Medium Priority-Medium Priority-Medium Priority-Medium Priority-Medium Priority-Medium Priority-Medium Priority-Medium Priority-Medium Priority-Medium Priority-Medium Priority-Medium Priority-Medium Priority-Medium Priority-Medium Priority-Medium Priority-Medium Priority-Medium Priority-Medium Priority-Medium Priority-Medium Priority-Medium Priority-Medium Priority-Medium Priority-Medium Priority-Medium Priority-Medium Priority-Medium Priority-Medium Type-Defect Type-Defect Type-Defect Type-Defect Type-Defect Type-Defect Type-Defect Type-Defect Type-Defect Type-Defect Type-Defect Type-Defect Type-Defect Type-Defect Type-Defect Type-Defect Type-Defect Type-Defect Type-Defect Type-Defect Type-Defect Type-Defect Type-Defect Type-Defect Type-Defect Type-Defect Type-Defect Type-Defect Type-Defect Type-Defect Type-Defect Type-Defect Type-Defect Type-Defect Type-Defect Type-Defect Type-Defect Type-Defect Type-Defect Type-Defect Type-Defect Type-Defect Type-Defect Type-Defect Type-Defect Type-Defect Type-Defect Type-Defect

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: fergalmoran/chrometophone#51