EAS build is failing since today's scheduled maintenance

Earlier today, there was scheduled maintenance according to the Apple Developer system status page: https://developer.apple.com/system-status/

Since that maintenance, Expo's eas build service has been failing. When attempting to sign into my Apple Developer account, I get the following message:

Authentication with Apple Developer Portal failed!
Apple provided the following error info:
Service not available because of maintenance activities, please try again after some time.

It appears that there are quite a few others having this same issue based on discussion on Expo's Discord server. Was this due to an update to the App Store Connect API during today's schedule maintenance? Is anyone at Apple looking at this issue? Any suggested fixes?

Answered by gr4h4m in 750383022

The Expo team released a fix via the EAS CLI. You’ll need to update to the latest:

npm install -g eas-cli

This should be the close of this issue for now.

Hey! I managed to start the building process after hitting "No" when asking for login into my developer account, but the process is stopped in the "Run fastlane" step with the error "Looks like fastlane ran into a build/archive error with your project". Do you think this is related to the outage we are facing?

This issue still persists today.

If you change your eas config at all then you can't use the "No" login solution and are screwed. You will get an error that the integrity of your app cannot be verified;

please fix this issue!

Accepted Answer

The Expo team released a fix via the EAS CLI. You’ll need to update to the latest:

npm install -g eas-cli

This should be the close of this issue for now.

There's a recent update from expo that fixes this issue, you should update your eas cli and try again

i Still having this problem: Authentication with Apple Developer Portal failed! UnexpectedAppleResponse: Apple provided the following error info: Service not available because of maintenance activities, please try again after some time.

For me it worked after running the command

npm install -g eas-cli --force

Re run "npm install -g eas-cli" fixed the issue.

This issue still persists

I still experience the issue. Please provide more information if possible.

Today I get the same error

I was able to fix it using yarn command instead.

yarn global add eas-cli

EAS build is failing since today's scheduled maintenance
 
 
Q