Hi, if you call StartNotify() right after a device disappears, bluez returns an org.bluez.Error.InProgress, even though the device isn't there at all. A simple fix is checking the case of !gatt at the very beginning of function characteristic_start_notify, since we can return the correct error immediately. The patch returns an Error.NotConnected, which I think is the correct error in this case, but it can be problematic since this function never returned that before. Another possible error is Error.Failed with the message "Not connected" since that's already expected from the function. This patch also cancels out the cleaning of client at the bottom of the function, since we never create it in the first place when a device is not available. cheers. Ahmed (1): Fix bug in characteristic_start_notify. src/gatt-client.c | 32 +++----------------------------- 1 file changed, 3 insertions(+), 29 deletions(-) -- 2.11.0 -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
