Apple compatibility
The special Profile Service protocol is primarily documented in Apple’s archived OTA guide. Current Apple Device Management documentation now focuses mostly on configuration profiles and MDM, so this project distinguishes three evidence levels:
- Documented: explicit in Apple Profile Service narrative or examples.
- Observed: verified on specified platform versions with reproducible fixtures.
- Extension: accepted losslessly but not yet normalized or claimed as Apple-defined.
0.1.0-beta.2 types the documented attribute names UDID, VERSION, PRODUCT, SERIAL, MEID, IMEI, ICCID, and MAC_ADDRESS_EN0. Availability depends on device hardware, OS, privacy behavior, and enrollment context. A requested value is not automatically guaranteed.
Apple Profile Service responses may use RSA/SHA-1. Apple’s archived guide requires a signed CMS response but does not prescribe the digest algorithm. Response verification accepts both RSA/SHA-1 and RSA/SHA-256.
When Apple adds a field, developers can use customDeviceAttribute and read raw without waiting for a release. A library update can then normalize it additively. Reserved structural fields cannot be overridden through extensions.
References
Section titled “References”- Profile Service payload and signed response
- Profile Service request/response plist examples
- Common payload keys
- Configuring multiple devices using profiles
References accessed 2026-08-24. Apple documentation and actual platform behavior take precedence over this independent implementation.