Unable to Verify App
An internet connection is required to verify trust of the developer "Apple Development: John Doe (ABCXYZ123)". This app will not be available until verified.
I've been getting this constantly over the last few weeks. It has been a real struggle to get anything done. Sometimes it goes away on its own after I try to launch the app a few times, but currently it's just staying down and I can't do any work.
Apparently there were issues with some Apple server ppq.apple.com before. They seem to be back, because trying again right now:
ping ppq.apple.com
PING use1-ppq-ext-prod.apple.com (17.33.200.235): 56 data bytes
Request timeout for icmp_seq 0
Request timeout for icmp_seq 1
^C
--- use1-ppq-ext-prod.apple.com ping statistics ---
3 packets transmitted, 0 packets received, 100.0% packet loss
ping apple.com
PING apple.com (17.253.144.10): 56 data bytes
64 bytes from 17.253.144.10: icmp_seq=0 ttl=60 time=9.776 ms
64 bytes from 17.253.144.10: icmp_seq=1 ttl=60 time=8.726 ms
^C
--- apple.com ping statistics ---
2 packets transmitted, 2 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 8.726/9.251/9.776/0.525 ms
This is incredibly disruptive. Surely there must be a way to disable this online verification? This is a development device that never leaves my desk and never installs any software except the things I build locally from my Mac (which I have trusted on the device).
The PPQ outage from last week [1] was a very specific thing and it’s definitely not related to whatever issue you’re hitting now.
Ping still fails
Testing with ping isn’t helpful in this case; AFAICT ppq.apple.com never responds to pings. Consider:
% ping ppq.apple.com
PING use1-ppq-ext-prod.sbz.apple.com (17.33.200.235): 56 data bytes
Request timeout for icmp_seq 0
Request timeout for icmp_seq 1
^C
--- use1-ppq-ext-prod.sbz.apple.com ping statistics ---
3 packets transmitted, 0 packets received, 100.0% packet loss
% curl -I http://ppq.apple.com
HTTP/1.1 301 Moved Permanently
…
Location: https://ppq-ext.v.aaplimg.com/
If you want to try out the redirect link, you have disable the client’s trust evaluation on the server:
% curl -I https://ppq-ext.v.aaplimg.com/
curl: (60) SSL: no alternative certificate subject name matches target host name 'ppq-ext.v.aaplimg.com'
…
% curl -I --insecure https://ppq-ext.v.aaplimg.com/
HTTP/2 404
…
Of course, that only proves that the server is running, it doesn’t confirm that it’s running correctly. To do that you’d have to look at what’s happening on the client side.
The next time you see an issue that you believe is related to this, I encourage you to trigger a sysdiagnose on the device and file a bug with that log. And then post your bug number here, just for the record.
Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"
[1] See ppq.apple.com returning 502 Bad Gateway - Unable to verify developer apps on device.
