| Previous | Next |
| STATUS_BTH_ATT_PREPARE_QUEUE_FULL | STATUS_BTH_ATT_ATTRIBUTE_NOT_LONG |
STATUS_BTH_ATT_ATTRIBUTE_NOT_FOUND
This can be a normal discovery boundary rather than a device failure
STATUS_BTH_ATT_ATTRIBUTE_NOT_FOUND is ATT error 0x0A. In discovery procedures, it tells the client that no attribute of the requested type exists within the handle range supplied in that request.
That can be the expected signal that a Find Information, Read By Type, or Read By Group Type scan has exhausted the remaining range. It becomes an error in the application sense only when the client expected a particular service, characteristic, or descriptor to be present there.
What to check
- Keep the starting and ending handles, the requested type UUID, the last successful discovery response, and whether the client was continuing a paged scan.
- Treat the result as an end-of-range condition only when the preceding discovery sequence and expected profile layout support that conclusion.
- If a required attribute is absent, compare the advertised services and device firmware/profile variant rather than guessing a handle from another model.
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.