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

Issue 602015 link

Starred by 2 users

Issue metadata

Status: Duplicate
Merged: issue 602189
Owner:
Not currently working on Chromium
Closed: Apr 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 3
Type: Bug



Sign in to add a comment

Web Bluetooth pairing screen crash, Chrome Dev for Android v51.0.2700.2

Reported by peter.os...@gmail.com, Apr 9 2016

Issue description

Chrome Version       : Chrome Dev for Android, v51.0.2700.2
URLs (if applicable) : N/A
Other browsers tested:
  Add OK or FAIL, along with the version, after other browsers where you
have tested this issue:
     Safari: N/A
    Firefox: N/A
         IE: N/A

What steps will reproduce the problem?
(1) Run this Web Bluetooth drone demo locally: https://github.com/poshaughnessy/web-bluetooth-parrot-drone
(2) Enable port forwarding and access the site at http://localhost:8080
(3) Press the 'Connect' button

What is the expected result?
 - That the pairing screen is shown, with my Travis mini drone listed, and that I can tap on it to pair with it.

What happens instead?
 - The pairing screen hangs on the loading spinner briefly, then the browser crashes with "Unfortunately, Chrome Dev has stopped."

Please provide any additional information below. Attach a screenshot if
possible.
 - This worked successfully with Chrome Dev v51.0.2693.2 when I tried on April 3rd. 
 - Attaching screenshots and output from `adb logcat -v time | grep -E " |[Bb]luetooth|cr.Bluetooth|BtGatt|BluetoothGatt|bt_btif_config"`.

 
chrome-dev-web-bluetooth-adb-logcat-filtered.txt
113 KB View Download
bug-1.png
109 KB View Download
bug-2.png
74.8 KB View Download
bug-3.png
1.4 MB View Download
Labels: OS-Android
Cc: finnur@chromium.org
Components: Blink>Bluetooth
Owner: scheib@chromium.org
Status: Assigned (was: Unconfirmed)
Cc: yfried...@chromium.org
Labels: Stability-Crash

Comment 4 by ortuno@chromium.org, Apr 23 2016

Might be  Issue 602189 

Comment 5 by ortuno@chromium.org, Apr 23 2016

Mergedinto: 602189
Status: Duplicate (was: Assigned)
Yeah that's totally it. Thanks for the detailed report though! The fix should be included in the next dev release.

Sign in to add a comment