This is not a "red herring". We are having devices fail on this as well. The failing iPads go through a 301 redirect when attempting to hit Apple’s PPQ verification site. When trying to GET from https://ppq.apple.com/v1/connect , the device is redirected to ppq-ext.v.aaplimg.com, causing verification to fail. Devices that are not failing to verify our enterprise apps are not being redirected.
Take a look at the video and information here: https://www.dropbox.com/scl/fo/0k2v4bf7851trk8yql56r/h?rlkey=h2pmax86ccokytijzojmmpn4j&dl=0
andydylan
Users receive reputation points by contributing quality content to the forums.
Posts include post and replies published on the forums.
Post authors can mark replies as Accepted to indicate successful solutions.
Apple Developer Forums admins can mark replies as Apple Recommended to indicate an approved solution
Last seen
Post
Replies
Boosts
Views
Activity
This is not a "red herring". We are having devices fail on this as well. The failing iPads go through a 301 redirect when attempting to hit Apple’s PPQ verification site. When trying to GET from https://ppq.apple.com/v1/connect , the device is redirected to ppq-ext.v.aaplimg.com, causing verification to fail. Devices that are not failing to verify our enterprise apps are not being redirected.
ppqfail.txt
ppqconnect.txt
same problem. opened a ticket with dev support but they never have any clue.