I’m experiencing the same issue and have tested several possible causes, including different network connections, proxy settings, and DNS resolution.
One of my test devices is an iPhone 6 running iOS 12.5.8, the latest iOS version available for that model. The login process fails at this endpoint:
https://buy.itunes.apple.com/WebObjects/MZFinance.woa/wa/authenticate?guid=mydeviceid
Normally, I would expect the authentication flow to redirect to an assigned pod/server, such as a pXX-buy.itunes.apple.com address. Recently, however, I have encountered all of the following responses:
- 301 Moved Permanently, without a Location header.
- 503 Service Temporarily Unavailable.
- 404 Not Found.
- 204 No Content, with an empty response body.
Some responses include X-XSS-Protection: 1; mode=block, but provide no useful explanation of why authentication failed.
Initially, the same account successfully signed in twice before I enabled a proxy. After enabling it, authentication started failing. I also confirmed that this hostname resolves to different server addresses in different regions. However, the failures now persist, so I cannot confidently attribute the problem to DNS or the proxy alone.
The most frustrating part is that another older iPhone could still sign in initially. After signing out and back in a few times while testing, that device also became unable to sign in and now encounters the same repeated errors.
I have seen similar reports in other communities. This makes me wonder whether Apple has changed something in the authentication backend or its handling of older clients, although I have no confirmation of a policy change.
Could Apple investigate this authentication endpoint and clarify whether App Store sign-in is still supported on iOS 12.5.8? If it is supported, is there a known fix or workaround? It is extremely frustrating to lose access on devices that were successfully signing in shortly before these failures began.