I'm trying to setup a macOS 26 build environment in a VM (using UTM and the virtualization framework Apple provides).
I have Xcode 26 installed and have logged into my Apple ID and verified that the team and other configuration looks fine in Xcode settings.
When trying to build the macOS app, I see errors saying the VM's device ID has not been registered. I have confirmed that the device ID is registered both in the Provisioning portal AND the downloaded .provisionprofiles (in Library > Developer > Xcode > UserData).
This problem appears on multiple targets (e.g. the main app and extensions).
If I try to manually provision the app, using the Provisioning portal, I can build the product, but it will not launch because of Gatekeeper issues.
Finally, signing to run locally doesn't work either. As the app launches, frameworks refuse to load because Team IDs don't match. With ad hoc provisioning, there are no Team IDs.
I've come to the conclusion that this just isn't possible.
Which is a shame because I need to support products with a build environment on macOS 15 and cannot move over to macOS 26 yet. I suspect many developers outside of Apple are in a similar position.
Certificates, Identifiers & Profiles
RSS for tagDiscuss the technical details of security certificates, identifiers, and profiles used by the OS to ensure validity of apps and services on device.
Selecting any option will automatically load the page
Post
Replies
Boosts
Views
Activity
Since this evening (March 10, 2026), I'm unable to launch any developer-signed app on my physical device (iPhone 16 Pro Max, iOS 26.4 beta 23E5223k). The error is:
"Unable to launch [app] because it has an invalid code signature, inadequate entitlements or its profile has not been explicitly trusted by the user."
On the device itself, it shows: "Unable to Verify App - An internet connection is required to verify the trust of the developer."
What I've tried:
Created a new Apple Development certificate
Deleted and reinstalled the app
Restarted the device
Tested on both Wi-Fi and cellular
Confirmed Developer Mode is enabled
Removed all third-party CA certificates from the device
Verified the code signature is valid (codesign -dv shows correct Authority chain)
The root cause:
https://ppq.apple.com is currently returning 502 Bad Gateway. I confirmed this both from my Mac (curl -s -o /dev/null -w "%{http_code}" https://ppq.apple.com → 502) and from Safari on the device.
This affects all developer-signed apps, not just a specific project.
Is anyone else experiencing this? Is there an ETA for the fix?
Environment:
Xcode 26.3 (17C519)
macOS 26.3.1 (25D2128)
iPhone 16 Pro Max, iOS 26.4 (23E5223k)
Topic:
Code Signing
SubTopic:
Certificates, Identifiers & Profiles