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

Issue 918063 link

Starred by 2 users
Status: WontFix
Owner: ----
Closed: Dec 28
Cc:
█ jlklein@chromium.org
sdantul...@chromium.org
mkarkada@chromium.org
dhadd...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

Failed to detect new phone on connect to your phone screen

Project Member Reported by abod...@chromium.org, Dec 28 
Chrome OS 11316.47.0, 72.0.3626.37


Please specify Cr-* of the system to which this bug/feature applies (add
the label below).

Steps To Reproduce:
(1)Enable unified setup with phone(Samsung 9s) on Chromebook 
(2)Change phone to another new phone (Pixel XL)(deleted account info at old phone)  
(3)Try to unified setup with new phone on Chromebook 

Expected Result:

Actual Result:
shows old phone name at connect your phone -> device detected
No luck after the forget device from the setting page. 

feedback: https://listnr.corp.google.com/product/208/report/85872168159?dateRange=All
 
How frequently does this problem reproduce? (Always, sometimes, hard to
reproduce?)

What is the impact to the user, and is there a workaround? If so, what is
it?

Please provide any additional information below. Attach a screen shot or
log if possible.

For graphics-related bugs, please copy/paste the contents of the about:gpu
page at the end of this report.

Comment 1 by jlklein@chromium.org, Dec 28 

Hi Ansar, when you forget the old device and try to set up the new one, are you saying that the Pixel XL does not show up in the dropdown on the first setup screen? See attached screenshot.
2018-12-26.png
183 KB View Download

Comment 2 by abod...@chromium.org, Dec 28 

yes, drop-down list is not showing.

Comment 3 by abod...@chromium.org, Dec 28 

see attached screenshot from the device.
unified setup.jpeg
241 KB View Download

Comment 4 by abod...@chromium.org, Dec 28 

Thank you Jeremy! I can see new phone details at dropdown list once i dialed *#*#2884936#*#* from the phone.

Comment 5 by jlklein@chromium.org, Dec 28 

Thanks for your patience on this, Ansar. I'm having trouble tracking down the other bug or threads where this was discussed, but the case is the following:

1) User gets new phone that's on an older version of GmsCore.
2) Device enrolls with cryptauth, but Better Together isn't supported on that version of gmscore.
3) GmsCore updates and now Better Together is supported, but the phone won't enroll again for another ~30 days.

Unfortunately, for now this is considered WAI. Eventually, things will get synced and work properly, but there's not a ton we can do to avoid this case without a really big spike when updating to whatever gmscore version we make this fix in :-/. We can try to do some clever rollouts with phenotype flags, but I'm not sure it's really worth the effort right now.

Comment 6 by jlklein@chromium.org, Dec 28

Status: WontFix (was: Untriaged)
►

Sign in to add a comment