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

Issue 758052 link

Starred by 1 user
Status: WontFix
Owner:
khorimoto@chromium.org
Closed: Aug 2017
Cc:
█ jlklein@chromium.org
█ lesliewatkins@chromium.org
r...@chromium.org
█ sonnysasaka@chromium.org
█ mcchou@chromium.org
khorimoto@chromium.org
jhawkins@chromium.org
hansberry@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

Add workaround for GATT characteristic bug

Project Member Reported by khorimoto@chromium.org, Aug 23 2017 
Issue 758051 prevents GATT characteristics from being inspected when multiple GATT connections are open at the same time.

It is unlikely that this bug will be fixed for M-61 since there are higher priority bugs to get fixed in this time frame. Thus, we should work around this bug for M-61.

To work around this issue, I plan on setting a timeout in this situation, then re-checking after the timeout is complete. Because this race condition only occurs if the timing is *just* right, we should be able to avoid this issue by waiting.

Comment 1 by khorimoto@chromium.org, Aug 23 2017

Status: WontFix (was: Started)
Unfortunately, I just tried out this fix, but it does not solve anything. It looks like if the GATT connection is created at this inopportune time, there is nothing we can do except give up and create a new GATT connection.

 Issue 758015  should serve as a workaround for this issue in the meantime.
►

Sign in to add a comment