| Previous | Next |
| STATUS_BTH_ATT_INVALID_HANDLE | STATUS_BTH_ATT_WRITE_NOT_PERMITTED |
STATUS_BTH_ATT_READ_NOT_PERMITTED
A valid attribute was addressed, but reading is not an allowed operation
STATUS_BTH_ATT_READ_NOT_PERMITTED represents ATT error 0x02. It is returned when the attribute can be located but its access permissions do not allow the requested read operation.
That distinction matters: an application can discover a characteristic or descriptor and still be unable to read its value. Pairing again does not turn a write-only or server-only attribute into a readable one; this status is separate from the ATT security errors for authentication, authorization, encryption, and key size.
What to check
- Keep the service UUID, characteristic or descriptor UUID, handle, requested ATT opcode, and advertised characteristic properties together in the diagnostic record.
- Confirm that the client selected the intended value handle rather than a declaration or descriptor handle.
- Use a read procedure only when the published profile permits it; do not probe repeatedly in the hope that a protocol permission changes.
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.