Issue metadata
Sign in to add a comment
|
newblue: gattClientConnect doesn't call the callback if it's already connected |
||||||||||||||||||||||||
Issue descriptionClients call gattClientConnect(address, callback) expecting that the callback will be called. But the callback will never be called if somehow the GATT connection already exists. This is difficult for clients because clients don't know whether to expect callback being called or not.
,
Oct 9
,
Nov 26
|
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by sonnysasaka@chromium.org
, Sep 19Components: OS>Systems>Bluetooth
Labels: -Pri-3 OS-Chrome Pri-1
Owner: dmitrygr@google.com
Status: Assigned (was: asi)