ppq.apple.com returning 502 Bad Gateway - Unable to verify developer apps on device

Code Signing Certificates, Identifiers & Profiles

This thread has been locked by a moderator; it no longer accepts new replies.

Created 1w

Replies 139

Boosts 172

Views 11k

Participants 128

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)

Answered by DTS Engineer in 879488022

Well, that was exciting |-:

It looks like Apple fixed the issue.

Yep.

I can’t really go into details here, other than to say that:

ppq.apple.com is a service on the critical path for the trusted execution of code in some situations [1].
It was having problems.
Those are now fixed.

I don’t have time to read through all 10 pages of posts on this thread. So, if there’s something you want to draw my attention to here, I recommend that you start a new thread with the details.

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

[1] There might be more info about it on the enterprise support side of things, but the only developer-focused reference I could find for it was in an old Xcode help page: Manually trust a developer on iOS.

Boost

DTS Engineer OP

Apple

Recommended

Well, that was exciting |-:

It looks like Apple fixed the issue.

Yep.

I can’t really go into details here, other than to say that:

ppq.apple.com is a service on the critical path for the trusted execution of code in some situations [1].
It was having problems.
Those are now fixed.

I don’t have time to read through all 10 pages of posts on this thread. So, if there’s something you want to draw my attention to here, I recommend that you start a new thread with the details.

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

statemachinejunkie OP

Quinn, I met you face-to-face back in 2005. Glad you are still around.

broncha OP

This is strange! no body seems to mention it, but I get redirected to https://ppq-ext.v.aaplimg.com/ which in turn throws a SSL mismatch error!

$ curl -I ppq.apple.com

HTTP/1.1 301 Moved Permanently

Server: Apple

Date: Mon, 16 Mar 2026 12:11:11 GMT

Content-Type: text/html

Content-Length: 162

Connection: keep-alive

Location: https://ppq-ext.v.aaplimg.com/

$ curl https://ppq-ext.v.aaplimg.com/

curl: (60) SSL: no alternative certificate subject name matches target host name 'ppq-ext.v.aaplimg.com' More details here: https://curl.se/docs/sslcerts.html

curl failed to verify the legitimacy of the server and therefore could not establish a secure connection to it. To learn more about this situation and how to fix it, please visit the web page mentioned above.

DTS Engineer OP

Apple

The outage described in this thread was resolved on the same day that it occurred.

If you’re working in an Enterprise team and having problems deploying your apps, I recommend that you seek help from either your MDM vendor or, if you’re doing this yourself, from Apple Support. You can also see community help over in the Apple Support Community, and specifically in the Business and Education topic area, where you’re more likely to find folks with enterprise app deployment experience.

I’m locking this thread because a) the issue it covered is most definitely resolved, and b) I don’t want it to become a distraction for folks who have enterprise deployment problems.

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"