Re: Clarification on ble_gattc_*_by_uuid calls

On Mon, Jun 27, 2016 at 04:13:09PM -0700, Simon Ratner wrote: > Hi Chris, > > One quick clarification question: after receiving a callback with any > error status, do you guarantee that the callback will never be called > again (including with a NULL svc param)? Hi Simon, Yes, that is the

Re: Clarification on ble_gattc_*_by_uuid calls

I agree it would be better to pass a status of BLE_HS_EDONE rather than 0 in this case. I will include this in the list of API-breaking changes that I think should be made to the Nimble host. Thanks, Chris On Mon, Jun 20, 2016 at 3:06 PM, Simon Ratner wrote: > Oh, interesting.

Re: Clarification on ble_gattc_*_by_uuid calls

Actually I think I just realised that might be what the mystery second callback in https://issues.apache.org/jira/browse/MYNEWT-326 is. Is that actually the "done" callback that just fails to set the error param correctly? On Mon, Jun 20, 2016 at 2:32 PM, Simon Ratner wrote: >

Clarification on ble_gattc_*_by_uuid calls

Hi devs, It appear that when I call ble_gattc_disc_svc_by_uuid with a service id that the device does not implement, I don't get any indication that is the case. No callback, no error, just sits there holding up the connection resources. Same deal with ble_gattc_read_by_uuid. I would've