We request clarification of the supported Core Bluetooth API contract for one specific call: publishing the Bluetooth Low Energy HID Report Reference descriptor (0x2908) using CBMutableDescriptor on iOS.
Our iPhone application uses CBPeripheralManager to publish a Human Interface Device over GATT Profile (HOGP) service for an iPad. Its Report characteristics use two-byte Report Reference values containing the report ID and report type. The relevant call is:
let reportReference = CBMutableDescriptor(
type: CBUUID(string: "00002908-0000-1000-8000-00805F9B34FB"),
value: Data([0x01, 0x01])
)
The initializer documentation lists only CBUUIDCharacteristicUserDescriptionString and CBUUIDCharacteristicFormatString as supported types. The iPhoneOS 27.2 SDK CBDescriptor.h also limits supported mutable descriptors to those types. This appears to exclude Report Reference.
Is constructing and publishing 0x2908 in this way officially supported on iOS? If yes, please identify the supported OS versions, value format, restrictions, and an authoritative document or sample. Does spelling the assigned UUID in its full Bluetooth-base 128-bit form change the support contract? If it is unsupported, please confirm that runtime acceptance should not be relied on, and whether a documentation correction or API enhancement request is appropriate.
Existing physical-device records from the full application include remote descriptor reads and notification subscriptions through an independent Central application. The owner also reports successful input, automatic reconnection and a 60-minute session after initiating a connection with nRF Connect. These are observations, not evidence of a supported API contract or a verified bonding sequence. They are not results from the attached reduced sample.
The attached ReportReferenceProbe.swift isolates construction and an add-service request. It does not advertise or send input and is not a complete HOGP implementation. It has been compiled to an object file against the iPhoneOS SDK but has not been linked, installed or run on a device. No runtime error or success is claimed for it. A didAdd error would not, by itself, identify the descriptor as the rejected attribute because other required HID attributes are omitted. A successful callback would not prove official support or remote visibility.
Please answer the API-support question independently of our observed interoperability. We are not asking for private APIs or an App Review approval prediction.
Attachments: ReportReferenceProbe.swift, README.en.md, ENVIRONMENT.en.md.
References:
- https://developer.apple.com/documentation/corebluetooth/cbmutabledescriptor
- https://developer.apple.com/documentation/corebluetooth/cbmutabledescriptor/init(type:value:)