Declarative Management Activations do not recover from failure

Question

Hamer3 OP

Created 1d

Replies 2

Boosts 0

Participants 2

Hello All,

I am currently developing a mobile management system using declarative management and for the most part it is pretty great. There is one consistent issue I have run into and it comes when testing VPP app installs with not enough licenses.

When my server detects that it can't provide a license ID it will return a 404, which causes the rest of the DM syncing to stop, and the activation to throw an error.

Per the documentation for using simple activation:

An array of strings that specify the identifiers of configurations to install. A failure to install one of the configurations doesn’t prevent other configurations from installing

The above would imply that if a config fails it should not affect anything else (aside from possibly reporting an error.

Am I returning the wrong error code for it to continue or is the behavior correct and the documentation is wrong?

Any additional info would be useful

Boost

Answer 1

Device Management Engineer OP

Apple

1d

What request to your server is generating a 404? If it is the request to fetch the app.managed configuration, then if that is missing, any activation that has a reference to it will fail to activate, and that it turn means none of the configurations referenced by those activations will apply.

I would suggest that you suppress putting the app.managed configuration in the device's DDM manifest until after you know the license is available.

1

Answer 2

Hamer3 OP

17h

Hello and thanks for the reply,

The 404 is returned when the device reaches out to fetch the associated app configuration, but during the config creation it is discovered that no licenses are available. I take it from the documentation it is implied that the failure of applying the configuration does not block other activations, rather than failure to fetch a configuration then?

I'll take that advice onboard thank you agin for answering

0