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

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)

same here. unable to verify

goddamm I wish id found this earlier. just spent so long banging my head against the desk on this.

Hi, I'ts the same from my side :-(

Guys at Apple, please get this fixed quickly, deadlines are burning :-)

I've gotten OK, Bad-Gateway, Gateway Time-Out on four different systems. Even when OK is returned, it takes a while to get a response. This started almost exactly at 10am pacific time for me. Like many of you I used the security command line to check my certs, checked my firewall (PFSense), and even switch my build system and my target iPad to use my iPhone personal hot-spot, in order to bypass my infrastructure and still, no-joy. After reading your posts, I have become convinced that this is an Apple services issue, even though their status page says everything is working.

More information. I have another project (Project-B) I'm working on, which is being developed on a different machine. Project-B installs on the same target iPad with no issues. I migrated the failing project (Project-A) over to this machine and added the missing certificates to the keychain so that the failing project would build. Even on this second system, I'm consistently getting the error for project-a but not for project-b. So, apparently this failure is specific to the type of certificate or provisioning for the target app, it seams.

Project-A: Hardware app using DriverKit, custom USB hardware, microphone, camera, etc. Only viable on iPadOS with an M-Processor.

Project-B: SwiftUI, SwiftData, document-based. Does use a FLIR camera but does not require DriverKit. Also uses microphone and camera.

Are any of you using DriverKit or working with anything that corresponds to Project-A? Have you tried build a simple sample app that does nothing special; does it work?

11

I’m seeing the same issue here.

Started on March 10, 2026, and it seems to affect all developer-signed apps on physical devices. I’ve reproduced it across multiple apps and devices after trying the usual fixes.

On-device, my message is:

Unable to Verify App An internet connection is required to verify the trust of the developer cert

It looks like an Apple-side verification outage affecting dev app trust and certs.

Would be great to get confirmation from Apple and an ETA for resolution.

Same problem here, raised a support ticket a few hours ago for this. Tried different device combinations, profiles, accounts, new certs, networks etc. Hopefully Apple will fix this soon.

Same here. Started about two hours ago for me.

Same error, for ~2hrs now.

But curl returns successful, confusingly.

curl -v https://ppq.apple.com

  • Host ppq.apple.com:443 was resolved.
  • IPv6: (none)
  • IPv4: 17.33.192.136, 17.33.193.105, 17.33.194.109
  • Trying 17.33.192.136:443...
  • Connected to ppq.apple.com (17.33.192.136) port 443
  • ALPN: curl offers h2,http/1.1
  • (304) (OUT), TLS handshake, Client hello (1):
  • CAfile: /Library/Frameworks/Python.framework/Versions/3.13/lib/python3.13/site-packages/certifi/cacert.pem
  • CApath: none
  • (304) (IN), TLS handshake, Server hello (2):
  • (304) (IN), TLS handshake, Unknown (8):
  • (304) (IN), TLS handshake, Certificate (11):
  • (304) (IN), TLS handshake, CERT verify (15):
  • (304) (IN), TLS handshake, Finished (20):
  • (304) (OUT), TLS handshake, Finished (20):
  • SSL connection using TLSv1.3 / AEAD-AES256-GCM-SHA384 / [blank] / UNDEF
  • ALPN: server accepted h2
  • Server certificate:
  • subject: CN=ppq.apple.com; O=Apple Inc.; ST=California; C=US
  • start date: Jan 21 17:47:41 2026 GMT
  • expire date: Feb 17 18:28:16 2027 GMT
  • subjectAltName: host "ppq.apple.com" matched cert's "ppq.apple.com"
  • issuer: CN=Apple Server Authentication CA; OU=Certification Authority; O=Apple Inc.; C=US
  • SSL certificate verify ok.
  • using HTTP/2
  • [HTTP/2] [1] OPENED stream for https://ppq.apple.com/
  • [HTTP/2] [1] [:method: GET]
  • [HTTP/2] [1] [:scheme: https]
  • [HTTP/2] [1] [:authority: ppq.apple.com]
  • [HTTP/2] [1] [:path: /]
  • [HTTP/2] [1] [user-agent: curl/8.7.1]
  • [HTTP/2] [1] [accept: /]

GET / HTTP/2 Host: ppq.apple.com User-Agent: curl/8.7.1 Accept: /

  • Request completely sent off

< HTTP/2 200 < server: Apple < date: Tue, 10 Mar 2026 20:45:52 GMT < content-type: text/plain; charset=UTF-8 < content-length: 2 < x-b3-sampled: 1 < x-b3-spanid: XXX < x-b3-traceid: XXX < strict-transport-security: max-age=31536000; includeSubdomains < x-frame-options: SAMEORIGIN < x-content-type-options: nosniff < x-xss-protection: 1; mode=block <

  • Connection #0 to host ppq.apple.com left intact

ok%

Apple, help us!

Same for me, but with different Team IDs the experience is different. Some of them work, and some don’t.

Same problem. However, Apple's system status appears healthy. Urgent update needed.

Same issue here since this evening (March 10, 2026) on both iPhone and iPad, paid Apple Developer Program account.

After extensive troubleshooting — new certificates, new provisioning profiles, device restarts, testing on both Wi-Fi and cellular — I can confirm this is server-side.

https://ppq.apple.com is returning 502 Bad Gateway intermittently. It sometimes responds with "OK", which makes the issue harder to diagnose as it appears to be working when checked manually.

Awaiting a fix from Apple.

Same issue here, cannot launch my build on my phone, stuck in a verify loop.

Same problem.

Same here! Xcode 26.4 beta but also able to repro on 26.2

Attempted fix as detailed here:

https://developer.apple.com/forums/thread/800521

And purged my provisioning profiles as described in step 2:

Go to ~/Library/Developer/Xcode/UserData/Provisioning Profiles and delete all your profiles.

Reloaded xcode, and same issue

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