At the moment, when there are any managed codes on a device, we don't sync the unmanaged codes on the device as this can result in existing unmanaged codes on the device inadvertently being associated with managed codes being created. We are working on a long term fix that will remove this limitation.
This limitation is especially frustrating in cases where new managed codes being created conflict with existing unmanaged codes on the device. In these cases, the managed code will fail to set with a duplicate_code_on_device error, but you won't be able to see the unmanaged code on the device that's conflicting. API users have to remove any pending managed codes on the device (or wait for them to set without errors) before they can see updated unmanaged codes.
At the moment, when there are any managed codes on a device, we don't sync the unmanaged codes on the device as this can result in existing unmanaged codes on the device inadvertently being associated with managed codes being created. We are working on a long term fix that will remove this limitation.
This limitation is especially frustrating in cases where new managed codes being created conflict with existing unmanaged codes on the device. In these cases, the managed code will fail to set with a
duplicate_code_on_deviceerror, but you won't be able to see the unmanaged code on the device that's conflicting. API users have to remove any pending managed codes on the device (or wait for them to set without errors) before they can see updated unmanaged codes.