Stuck on connecting to gatt server, when trying to access Samsung Galaxy S6 via web bluetooth
Reported by
mitalexs...@gmail.com,
Mar 29 2018
|
||||
Issue descriptionChrome Version : 65.0.3325.181 OS Version: 10.0 URLs (if applicable) : https://googlechrome.github.io/samples/web-bluetooth/battery-level.html Other browsers tested: Add OK or FAIL after other browsers where you have tested this issue: Safari: Firefox: IE/Edge: What steps will reproduce the problem? 1. CLick on Get Bluetooth Device's Battery Level 2. Pair Samsung Galaxy S6 3. Browser is stuck on "Connecting to GATT Server..." 4. After a little while chrome crashes What is the expected result? I am using a Galaxy S6 as a Peripheral BLE device, through the BLE Peripheral Simulator app, in order to test web bluetooth functionality through the Chrome Browser running on Windows 10. The expected result is that I would read the battery level as it's notified by the Peripheral simulator app. What happens instead of that? The browser just gets stuck on "Connecting to GATT Server..." and it does not read anything. End result is - Chrome crashes after trying to connect for awhile. Please provide any additional information below. Attach a screenshot if possible. UserAgentString: Chrome/65.0.3325.181
,
Mar 30 2018
As this issue requires Samsung Galaxy S6 mobile to test this issue , adding TE-NeedsTriageFromHYD label for further checking from Android team. Could someone from Inhouse team please have a look at this issue. @Reporter: Please provide crash id by navigating to chrome://crashes.
,
Mar 30 2018
Crash id is: 84d9209c-f27d-4e50-8985-6a1bb907a72b
,
Apr 3 2018
Tested the issue using #65.0.3325.181 on Win 10 and connected a real device (Samsung Galaxy S6, 6.0.1 #65.0.3325.109. Below are the observations. 1. Navigated to https://googlechrome.github.io/samples/web-bluetooth/battery-level.html 2. Paired Samsung Galaxy S6 3. Didn't connect to any server 4. No ANR and Crash is seen @mitalexster: Could you please help us with a sample Crash I'd from chrome://crashes for further triaging of the issue? Thanks!!
,
May 25 2018
As there is no response from the reporter for more than one month. Hence, closing the issue as wontFix. Please feel free to raise a new issue if the issue is reproduced with latest chrome builds. The latest chrome builds can be downloaded from the below URL: https://www.chromium.org/getting-involved/dev-channel Thanks...!! |
||||
►
Sign in to add a comment |
||||
Comment 1 by viswa.karala@chromium.org
, Mar 29 2018