| Previous | Next |
| STATUS_BTH_ATT_WRITE_NOT_PERMITTED | STATUS_BTH_ATT_INSUFFICIENT_AUTHENTICATION |
STATUS_BTH_ATT_INVALID_PDU
This is a framing or request-format failure at the ATT layer
STATUS_BTH_ATT_INVALID_PDU maps to ATT error 0x04. It means the server could not accept the received Attribute Protocol data unit as a well-formed request, before any normal attribute operation could be completed.
Treat it as a protocol-construction problem, not as evidence that a particular characteristic value is wrong. The request opcode, field layout, PDU length, and negotiated ATT MTU are more useful than the semantic contents of the intended attribute value.
What to check
- Record the raw ATT opcode, the complete PDU length, the negotiated MTU, transport logs, and the version of the client library or firmware that produced the request.
- Compare the exact request structure with the ATT procedure required by the profile; do not diagnose this as Invalid Attribute Value Length unless the server accepted a valid write request and rejected its value length.
- Check for truncation, an opcode used on the wrong channel or state, and a client/server feature mismatch before altering peripheral data.
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.