When you encounter the message ‘503 Service Temporarily Unavailable,’ it can be quite confusing, especially when you’re trying to log into your Apple ID using various Fastlane modules. This error indicates that the server is currently unable to handle the request, usually due to maintenance or overloading. Understanding this can help you remain patient while troubleshooting.
get_certificates aborts with:
<head><title>503 Service Temporarily Unavailable</title></head>
<body>
<center><h1>503 Service Temporarily Unavailable</h1></center>
<hr><center>Apple</center>
</body>
</html>
The problem seems to be related to the url:
fetch('https://idmsa.apple.com/appleauth/auth/signin', {
"headers": {
"content-type": "application/json",
'X-Requested-With': 'XMLHttpRequest',
'X-Apple-Widget-Key': 'e0b80c3bf78523bfe80974d320935bfa30add02e1bff88ec2166c6bd5a706c42',
'scnt':SCNT,
'X-APPLE-HC:HC,
'X-Apple-ID-Session-id,
'Accept': 'application/json, text/javascript'
},
"method": "POST",
"body": "{\"accountName\":\"" + username + "\",\"rememberMe\":false,\"password\":\"" + password + "\"}",
Apple now seems to be using a slightly different url
https://idmsa.apple.com/appleauth/auth/signin/complete
and also the POST body has changed to:
{"accountName":"foo@bar.com","rememberMe":false, "m1":"xxx","c":"yyy","m2":"zzz"}
where xxx,yyy,zzz seem to be randomly changing.
Actually, I could verify that 2 things currently do not work anymore:
a) Authenticating with username/password to trigger the 2FA process (to then use hashCash to generate the DES cookie)
b) using an actual valid DES cookie for authentication.
If you’re facing these authentication issues, here are some steps you can follow:
Gemfile
File inside the IOS File replacebundle install
, bundle update fastlane
, or bundle update
For more details Follow the this Link: GITHUB