| Previous | Next |
| STATUS_BTH_ATT_ATTRIBUTE_NOT_FOUND | STATUS_BTH_ATT_INSUFFICIENT_ENCRYPTION_KEY_SIZE |
STATUS_BTH_ATT_ATTRIBUTE_NOT_LONG
A long-value continuation procedure was used where it does not apply
STATUS_BTH_ATT_ATTRIBUTE_NOT_LONG corresponds to ATT error 0x0B. The Attribute Protocol allows a server to return it for a Read Blob request when the value is fixed-length and fits within a normal ATT response, so a blob continuation is not an appropriate read method.
It should not be interpreted as a generic statement that the device cannot handle large data. It describes the procedure selected for this particular attribute. Long writes use the Prepare Write and Execute Write procedures, not Read Blob.
What to check
- Log the target handle, Read Blob offset, ATT MTU, the preceding normal read result, and the value type expected by the profile.
- Stop the Read Blob loop for this attribute and use the ordinary read result when it already contains the complete fixed-size value.
- Do not convert this status into Invalid Offset; the server is rejecting the long-read procedure itself, not merely a position within a valid blob.
References
- Bluetooth SIG: Attribute Protocol (ATT)
- Bluetooth SIG: Generic Attribute Profile (GATT)
- Microsoft: Bluetooth GATT client
Looking for a different code? Search another status or error code.