| Previous | Next |
| STATUS_BTH_ATT_REQUEST_NOT_SUPPORTED | STATUS_BTH_ATT_INSUFFICIENT_AUTHORIZATION |
STATUS_BTH_ATT_INVALID_OFFSET
The handle and procedure can be valid while the value position is not
STATUS_BTH_ATT_INVALID_OFFSET represents ATT error 0x07. It arises when an operation that uses an attribute-value offset, such as a Read Blob request or a prepared write, specifies a position that the server cannot apply to that value.
For Read Blob, the ATT specification treats the offset as zero-based and distinguishes an offset beyond the value length from an offset exactly at the end. This error is therefore about the current value boundary, not about a bad handle or an MTU negotiation failure by itself.
What to check
- Log the handle, request type, offset, current known value length, negotiated MTU, and whether the client is resuming a fragmented operation.
- Refresh the value or profile-defined length before recalculating the next offset; do not infer the boundary only from a previous packet size.
- When a value can change during the session, use the profile's consistency rules rather than assuming a multi-request read sees an immutable byte array.
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.