Request failed with http status code 503

I believe I am experiencing the same issue described here, so I would like to add more details. In my iOS app, I implemented DeviceCheck token generation and server-side validation. On recent devices everything works as expected: the server validates the token successfully and returns status 200 along with the two bit values. However, on iPhone 6S running iOS 15.8.4 only, the request fails with: Request failed with status code 400 This happens consistently in both environments: Development: https://api.development.devicecheck.apple.com/v1 Production: https://api.devicecheck.apple.com/v1 On iPhone 6S, device.supported returns true, and the generated token is sent to the server. The token length is over 2000 characters (base64), and visually it looks similar to tokens from newer devices that work fine. So I don't think the app is failing to generate a token. Server side is implemented in TypeScript using jsonwebtoken: ^9.0

We can confirm this here from Germany, have been seeing issues since about 1 AM UTC in increasing amount (although that may also be due to our traffic fluctuations). Besides the alert internal error we also have had connection aborts, no response after our 6 second time out and the occasional HTTP 503 Unavailable error. Some servers in the DNS rotation seem to be affected more than others though. Apple developer status unfortunately doesn't show anything either and the normal apple status only a resolved issue between 3:16 and 4:45 which doesn't match our logs at all.

I changed the urls used from http://MacBook-Pro.local:8080 to the Mac's ip address:8080 and now get this error instead: configure failed Error Domain=com.apple.CipherML Code=1100 Unable to query status due to errors: failed to fetch token UserInfo={NSLocalizedDescription=Unable to query status due to errors: failed to fetch token, NSUnderlyingError=0x9fc845ef0 {Error Domain=CipherML.AuthenticationError Code=3 failed to fetch token UserInfo={NSLocalizedDescription=failed to fetch token}}} Presumably this has something to do with service-config.json contents: { issuerRequestUri: http://192.168.1.4:8080, users: [ { tier1: {} }, [ AAAA ], { tier2: {} }, [ BBBB, CCCC ] ], The instructions for this say For the userTierToken, please set it to one of the values that you added in the service configuration file in Running the service section. For example BBBB.

@Verara20 May we ask which app/AppClip is affected in your case? We are currently only experiencing this error with one AppClip, but another one (for a completely different app/development team) is working fine. So we are still trying to figure out why one works and the other doesn't. The app that isn't working for us is an unlisted app. At first, we thought that might be the reason, but we simply don't know. It's depressing that we can't do anything at the moment to get the solution working again with iOS26. The console log shows that there are some requests that are going wrong and that didn't happen with iOS18. error 15:05:16.940931+0200 appstored AMSURLSession: [F50720EC] Session decoder failed. Result = (null); Error = Error Domain=ASDErrorDomain Code=507 Invalid Response Status: 14501 UserInfo={NSDebugDescription=Invalid Response Status: 14501} error 15:05:16.940942+0200 appstored AMSURLSession: [F50720EC] Task completed with error = Error Domain=ASDErrorDoma

Thanks for the info.We actually have noticed an increase in the number of customer tickets about missing subscriptions in the account. For the past few days, we've been getting a lot of 503's from the receipt verification API. We're trying to re-request the verification a few times, but if it fails completely, the receipt is gone forever. This means that we'll have to add another system to store those receipts for later, but in the meantime, the customer can't access their purchased item...

Yes, starting this morning we're seeing intermittent 502, 503 and 404 errors. Still looking into it, but making the same requests minutes later sometimes works.

503 = Service Temporarily Unavailable. Is it available now? If not, raise a bug at: https://feedbackassistant.apple.com/ then post the FB number here.