Anyone know what the DeclarationType string values are for the Asset declarations?
UserIdentity asset defines the type as com.apple.asset.useridentity.
There is no such value for UserNameAndPasswordCredentials.
Has anyone been able to install this type of declaration?
Post not yet marked as solved
Hi Apple community,
We encountering an issue with Declarative Management app events when attempting bulk app distribution through our Mobile Device Management (MDM) solution.
Description of the Issue: During bulk app distribution, the expected app events defined in the Declarative Management framework are not functioning as intended. While individual app deployments work fine and trigger the desired events, the problem arises specifically when distributing apps in the bulk of more than 20 apps.
My Status-Subscription Configuration,
{
"Type": "com.apple.configuration.management.status-subscriptions",
"Identifier": "DEFAULT_STATUS_CONFIG_0",
"ServerToken": "2",
"Payload": {
"StatusItems": [
{
"Name": "account.list.caldav"
},
{
"Name": "account.list.carddav"
},
{
"Name": "account.list.exchange"
},
{
"Name": "account.list.google"
},
{
"Name": "account.list.ldap"
},
{
"Name": "account.list.mail.incoming"
},
{
"Name": "account.list.mail.outgoing"
},
{
"Name": "account.list.subscribed-calendar"
},
{
"Name": "device.identifier.serial-number"
},
{
"Name": "device.identifier.udid"
},
{
"Name": "device.model.family"
},
{
"Name": "device.model.identifier"
},
{
"Name": "device.model.marketing-name"
},
{
"Name": "device.operating-system.build-version"
},
{
"Name": "device.operating-system.family"
},
{
"Name": "device.operating-system.marketing-name"
},
{
"Name": "device.operating-system.supplemental.build-version"
},
{
"Name": "device.operating-system.supplemental.extra-version"
},
{
"Name": "device.operating-system.version"
},
{
"Name": "mdm.app"
},
{
"Name": "passcode.is-compliant"
},
{
"Name": "passcode.is-present"
}
]
}
}
Has anyone encountered a similar issue where Declarative Management app events fail to trigger during bulk app distribution? If so, I would greatly appreciate any insights, recommendations, or potential workarounds you may have discovered. Additionally, if you have any suggestions for further troubleshooting steps or resources to explore, please feel free to share them.
Thank you in advance for your time.
Post not yet marked as solved
Hello everyone,
I was trying out Declarative Device Management on my iOS 16 device to get a feeling of how it works. While trying out the new protocol i managed to find some bugs in the behavior of Declarative Device Management.
When subscribing to the "passcode.is-compliant" state the device initially sends the state "passcode.is-compliant==false" but will never (even after hours) send "passcode.is-compliant== true", even when the device is definately complying to a complex passcode policy and even when no passcode policy is present. This state also didn't work as a predicate for an activation in the form of "(@state(passcode.is-compliant) == TRUE)". The referenced configuration was never activated even after the device definately complied with the installed passcode policy.
When subscribing to the "passcode.is-present" state the device will initially send the correct state but then never update the state even when clearing the passcode and re entering it again multiple times and even after waiting for 10 minutes.
When using an activation with predicate "(@state(passcode.is-present) == TRUE)" the device will correctly install the referenced configuration but after removing the passcode it will not remove the configuration even though it should
After reenrolling the device and reactivating Declarative Device Management the device reported the state "passcode.is-present==true" even though the device didn't have a passcode present.
Can anyone else confirm this behavior?
Thanks and have a nice day
rweiss.