Hi. I can't contact the support as I still have a legacy enterprise instance. But I found a workaround. Following the "empty profile" error, I added another payload to the profile (in my context it was a restrictions payload) and then the profile started to deploy correctly. So I was eventually able to get my test devices set their User-Initiated Activation Lock. I didn't see the issue last summer because I originally had a Web Clip payload attached to the profile, which was removed afterwards. If someone at the support reads this message, there's something to check.
... View more