'Error 14 (0xe): GATT ERR UNLIKELY' after every notification about gobbledegook HOT 3 CLOSED

Sorry for the late response (thanks for the reminder in #10.) When this issue was originally opened, I spent about an hour on this issue, but got interrupted and apparently forgot to return to this issue.

I struggled with this same error when the project was in active development. Google searches didn't turn up anything useful. I did solve it back in the day (this was a year ago) but I don't exactly remember how. I poured through my git logs and code looking for a hint and may have found it:

The unlikely error message disappears from the todo.txt after a bugfix in the iOS code that was inadvertently sending too much data (20 bytes is the limit for a single BLE packet.)

In case this doesn't resolve it for you, here's as much information as I can remember:

• The error string "Error 14 (0xe): GATT ERR UNLIKELY" is received from the iOS device.
• For me, the error was sporadic
• I seem to recall that this error is the iOS catch-all for BLE errors. So even if I'm right about how I fixed it in my case, you may be receiving the error for an entirely different reason.
• At one point, I had modified the GGK code to ignore that error to avoid the disconnect and it worked fine.
• I have a vague memory that sending null terminators with strings was causing issues, and had to remove them. This may be a false lead, because I can't remember a reason why BLE would care.

from gobbledegook.

Hey,

Thanks for your response, and glad to see you back around here! 😃

I get this error either in Android and iOS devices. Apparently it doesn't hurt much, I can easily ignore it from the App in the device and all continues working fine. So if this is a generic error which might appear due an obscure reason then it will be hard to find and resolve. I can, indeed, live with it.

What it appears a more critical error is the one I exposed in my comment in #10: ERROR: Unsupported response event type: 0x0011 (Authentication failed event).

This error only appears on iOS devices and on latest Bluez versions (5.49 and 5.50). It's critical because it disconnects the session and makes completely unusable the BLE communication.

Do you have an idea if it can be fixed in your GGK library?

Thanks.

from gobbledegook.

Authentication/pairing/bonding isn't supported in GGK (I've never messed with it myself.)

So... if you're not intending to do any type of pairing then a good starting point would be to figure out why it is when that wasn't your intention.

Also, I seem to remember something about iOS 9.1 requiring an extra step (or slightly different procedure) to avoid the pairing requirement. Might be a place to start googling?

from gobbledegook.