New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 908242 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Last visit 25 days ago
Closed: Nov 28
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Feature



Sign in to add a comment

Missing ability to add new device for Better Together

Reported by mre2...@gmail.com, Nov 25

Issue description

UserAgent: Mozilla/5.0 (X11; CrOS x86_64 11264.0.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/72.0.3609.3 Safari/537.36
Platform: 11264.0.0 (Official Build) dev-channel cave

Steps to reproduce the problem:
1. Have an other/old device that was previously connected to your Chromebook and setup with Better Together.
2. Have a new device you want to setup to connect to your Chromebook via Better Together.
3. Disconnect old device from Chromebook/Better Together under connected devices in settings.
4. Attempt to connect new device by clicking "Set up" under connected devices in settings.
5. Only device shown on set up page is the old one. No option to add new one. 

What is the expected behavior?
Should be an option in the setup process that allows a new device to be setup.

What went wrong?
No ability to setup my new Pixel 3 XL after I had my 2 XL connected originally.

Did this work before? No 

Chrome version: 72.0.3609.3  Channel: dev
OS Version: 11264.0.0
Flash Version: 31.0.0.148
 
Components: UI>Multidevice
Cc: jhawkins@chromium.org jlklein@chromium.org jordynass@chromium.org khorimoto@chromium.org themaxli@chromium.org nohle@chromium.org hsuregan@chromium.org jessejames@google.com
Owner: jlklein@chromium.org
Thanks for the report! Do you mind going to chrome://proximity-auth on your Chromebook, clicking "save logs" and then upload those to this bug? That should give us some ability to see what's up here?

For reference, did you just get the new phone the same day you tried this? Is your chromebook still not able to see the new phone today?
proximity_auth_logs_2018-11-26T21_38_47.127Z.txt
38.8 KB View Download
I did just get the phone but it has been about 2-3 days and I still only see my old Pixel 2 XL and my old Pixel 3 XL.
Thanks for the quick response! Are you saying that you had a Pixel 2 XL set up with your Chromebook, then bought a Pixel 3 XL, then got a second Pixel 3 XL? I do see 2 Pixel 3 XLs in your logs, so I want to make sure I'm fully understanding the state here. Had you set up the first 3XL before trying to set up the second one? From the logs, it seems like you may have enabled the other 3XL and then disabled it again. Is that right?

I have a theory about what's going on here, but I just want to make sure I've got the details right here :-).
Yes. I has a Pixel 2 XL. Then I got a Pixel 3 XL. I wasn't able to add a new device through setup, but I was able to get it connected via a roundabout way that someone had posted on Reddit. Now, I had to get a replacement 3 XL and I cannot get that one to connect at all now.

I did re-setup the old 3 XL before I ran my logs hoping that the 3 XL that is listed in the drop down may have been the new one.

The attached screenshot shows my setup window in its current state when I attempt to add my new 3 XL. The 3 XL that is listed is the old one.
Screenshot 2018-11-26 at 8.16.31 PM.png
110 KB View Download
OK, thanks again. I think I do see what's going on here then. Your new phone just hasn't enrolled with our server yet after auto-updating Google Play Services from the version included in the system image. It will do so under normal circumstances within the next couple of weeks, but you can also force it by going to the dialer on your phone and typing *#*#2884936#*#*. Once that's done, going back over you your Chromebook for setup should work :-).
Great. I appreciate that. I didn't realize that was how it worked. I just assumed that you added the phone manually. Thanks for your help! 
By the way . . . I forced the CryptAuth enrollment and the 3 XL showed up in the setup window. Thanks again!
Status: WontFix (was: Unconfirmed)
Glad you got it working!

Sign in to add a comment