Bluetooth devices not visible
Reported by
kran...@gmail.com,
Jul 2 2016
|
||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_5) AppleWebKit/601.6.17 (KHTML, like Gecko) Version/9.1.1 Safari/601.6.17 Steps to reproduce the problem: 1. Go to https://googlechrome.github.io/samples/web-bluetooth/notifications.html 2. Enter service uuid and char uuid of a device that doesn't advertise the name in the adv packet. 3. Click start notifications. 4. Device is not visible in the popup. What is the expected behavior? Device should be visible in the selector. What went wrong? Is there issues scanning for devices that don't have name in the adv packet? Did this work before? N/A Chrome version: Version 54.0.2787.0 (64-bit) Channel: n/a OS Version: OS X 10.11.5 Flash Version: Shockwave Flash 22.0 r0
,
Jul 4 2016
,
Jul 4 2016
Moving this nonessential bug to the next milestone. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jul 6 2016
Could it be possible to get some logs? Here are the instructions: https://www.chromium.org/developers/how-tos/file-web-bluetooth-bugs
,
Apr 20 2017
Issues not modified in last 50 days aren't on track to ship in next release.
,
Apr 23 2018
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Apr 23 2018
|
||||||
►
Sign in to add a comment |
||||||
Comment 1 by durga.behera@chromium.org
, Jul 4 2016Labels: M-53
Status: Untriaged (was: Unconfirmed)