Note that there are some explanatory texts on larger screens.

plurals
  1. POIs it possible to programmatically access the error codes logged by CoreBluetooth?
    primarykey
    data
    text
    <p>I am implementing a BLE central device on the iPhone, using as peripheral a custom BLE device developed (whose firmware has been written by a colleague).</p> <p>The peripheral for some operation will return a BLE error code, conforming to the standard Bluetooth ATT error codes as defined in BLE specifications.</p> <p>On the iPhone side, where I'm using the CoreBluetooth stack to develop the central device, I am notified of such errors on the debugger output window of xCode as:</p> <p>CoreBluetooth[WARNING] Unknown error: XX</p> <p>and then I receive in the callbacks a CBError* object. My problem is that the CBError* object which I get in the callback (e.g., in CBPeripheralDelegate's didWriteValueForCharacteristic callback) just contains code=0 and localizedDescription="Unknown error".</p> <p><strong>Is it possible to retrieve somehow the error code which is logged on the debugger output window by the CoreBluetooth stack?</strong></p> <p>From my research it appears that CoreBluetooth maps almost all BLE standard error codes into "unknown errors" (with internal code 0, see <a href="https://developer.apple.com/library/ios/documentation/CoreBluetooth/Reference/CoreBluetooth_Constants/Reference/reference.html#//apple_ref/doc/uid/TP40011288-CHCBErrorhConstants-SW2">CBError reference</a>); I would like to get more detailed error codes, like those coded by <a href="https://developer.apple.com/library/ios/documentation/CoreBluetooth/Reference/CoreBluetooth_Constants/Reference/reference.html#//apple_ref/doc/uid/TP40011288-CHCBErrorhConstants-SW13">CBAttError</a>.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload