| Previous | Next |
| STATUS_BTH_ATT_INSUFFICIENT_ENCRYPTION_KEY_SIZE | STATUS_BTH_ATT_UNLIKELY |
STATUS_BTH_ATT_INVALID_ATTRIBUTE_VALUE_LENGTH
The server accepted the request structure but rejected the value size
STATUS_BTH_ATT_INVALID_ATTRIBUTE_VALUE_LENGTH maps to ATT error 0x0D. It means the operation reached an attribute whose value length is not valid for the request or the attribute's defined representation.
This differs from Invalid PDU: the ATT request can be well-formed and the handle can be valid, but a fixed-size descriptor, a profile-defined field, or the server's value constraints reject the supplied length. It is also different from a fragmentation error, which is normally reported as Invalid Offset when the offset is outside the value range.
What to check
- Record the write or read procedure, handle, total value length, fragment offset, negotiated ATT MTU, and the profile's expected field or descriptor length.
- Validate the exact byte representation, including optional fields and endian layout, before changing transport-level retry behavior.
- For a large value, confirm whether the profile expects a normal write, a prepared reliable write, or an application-specific framing layer.
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.