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

Issue 645023 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Oct 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Android , Mac
Pri: 1
Type: Bug

Blocking:
issue 421668



Sign in to add a comment

bluetooth: BluetoothDevice.uuids is empty while filtering by service UUID

Project Member Reported by fbeaufort@chromium.org, Sep 8 2016

Issue description

Version: 55.0.2853.0	
OS: Mac

What steps will reproduce the problem?
(1) Make sure a nearby Physical Web beacon (one with Physical Web blue logo on it) is in Config Mode
(2) Go to https://googlechrome.github.io/samples/web-bluetooth/device-info.html?service=ee0c2080-8786-40ba-ab96-99b91ac981d8
(3) Click "Get Bluetooth Device Info" button
(4) Pick device in bluetooth chooser

What is the expected output?
Bluetooth Device Allowed UUIDs should include "ee0c2080-8786-40ba-ab96-99b91ac981d8" as I'm filtering by its UUID (like it does on Chrome OS)

What do you see instead?
Allowed UUID is empty.

 
Screen Shot 2016-09-08 at 8.50.18 AM.png
158 KB View Download
Cc: scheib@chromium.org jlebel@chromium.org
Labels: OS-Android
Owner: ----
Status: Available (was: Assigned)
Note that I can also reproduce this issue on Android 7.0 Nougat.
7641181242011235523-account_id=2.png
288 KB View Download
This is happening because of the way we handle advertisements and their uuids.

When the user selects a device there is a chance the device is no longer advertising that UUID so we leave that field empty.

The solutions probably involves caching the advertised UUIDs in some way. The way we cache them will depend on the outcome of https://github.com/WebBluetoothCG/web-bluetooth/issues/290
Status: WontFix (was: Available)
Obsoleted by  issue 653317 .

Sign in to add a comment