- From: Emill via GitHub <sysbot+gh@w3.org>
- Date: Fri, 03 Feb 2017 23:37:50 +0000
- To: public-web-bluetooth-log@w3.org
Yes, CoreBluetooth is not so good in this case. But both solutions handles this wrong, i.e. you can get a read request's promise resolved with a notified value rather than the correct read response. We've actually sent a bug report to Apple telling them that it's impossible to distinguish between a read response and a notification. By the way, noble uses a lower level mechanism in Mac OS X to really solve this problem: https://github.com/sandeepmistry/noble/blob/cbe0213e5f9d02ce40e8873a44f1f9008c0d4397/lib/mac/yosemite.js#L522. It seems there is actually an isNotification parameter that is removed by the outer API. -- GitHub Notification of comment by Emill Please view or discuss this issue at https://github.com/WebBluetoothCG/web-bluetooth/issues/274#issuecomment-277392593 using your GitHub account
Received on Friday, 3 February 2017 23:37:56 UTC