I was able to add the new provisioning UDID to the portal, but I am still unable to run the app. thibault@guest % system_profiler SPHardwareDataType | grep Provisioning Provisioning UDID: bf96988f343e2b8be88782b9aa29e99ab622f243 thibault@guest % security cms -D -i ~/Desktop/Test.app/Contents/embedded.provisionprofile | grep -A 3 ProvisionedDevices <key>ProvisionedDevices</key> <array> <string>...</string> <string>BF96988F343E2B8BE88782B9AA29E99AB622F243</string> Despite the provisioning UDID correctly being in the provisioning profile, I get: embedded provisioning profile not valid: file:///Users/thibault/Desktop/Test.app/Contents/embedded.provisionprofile error: Error Domain=CPProfileManager Code=-212 "Provisioning profile does not allow this device." UserInfo={NSLocalizedDescription=Provisioning profile does not allow this device.} I even tried adding the hardware UUID, just in case, to no avail. Does it matter how the VM is created? Or should any VM using the macOS virtualisation framework work?