EAS build is failing since today's scheduled maintenance

Developer Tools & Services Xcode
gr4h4m OP
Created Apr ’23
Replies 38
Boosts 23
Views 25k
Participants 41

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.

Replies  38
Boosts  23
Views  25k
Participants  41
dooboolab OP
Apr ’23

I finally solved the issue reading this! Hope this helps! https://github.com/expo/eas-cli/issues/1672#issuecomment-1416851869

Just select no on login and it started building..

0
stalliveli OP
Apr ’23

Come on Apple, please fix this!

0
basnetech OP
Apr ’23

This is blocking us. Please resolve or provide a status update.

1
Kingsley_93 OP
Apr ’23

Hmm, any progress, did Apple fix it? It was > 48h since I first met this issue...

0
AndrewLeeDemi OP
Apr ’23

Same problem since Saturday. Please fix, Apple

1
john5634 OP
Apr ’23

Same issue this morning. That makes it almost 3 days with out even a whisper from Apple. I sent a bug report but it will be at least 1-2 days before I hear back.

This along with the recent WeatherKit issues (and lack or response or help) has made my dive into mobile development extremely frustrating and painted Apple in a bad light. What the hell are we paying our yearly fees for?! It sure aint for developer support or reliable services...

2
izi-developer OP
Apr ’23

feel like its my luck block entire developing, i was faced multply issues during build last week, and week later ive start fixing again now iam facing this boring issue. @support please fix it asap - iam so demotivated i cant delivery awesome app to my greatfull client

1
sanjeeva_framebridge OP
Apr ’23

Work around I found for this is to choose no for the login prompt in EAS build. Then downloading that IPA from builds section in your Expo account. And uploading that IPA through Transporter app.

2
amitr OP
Apr ’23

Same issue, more than 30 hours now.

0
gr4h4m OP
Apr ’23

The latest fix from all of the above discussion is to use this command eas build --profile production --local and say no to the "want to log in to your Apple account" question. You will then need to upload your .ipa manually. If you run into problems (e.g. if fastlane fails), you can try again without the --local flag.

If you want to do a development build instead of a production build, you will need to download your distribution certificate and provisioning profile from the expo site (Project > Credentials > iOS > Application Identifier) and place those details in a credentials.json file (see https://docs.expo.dev/app-signing/local-credentials/).

0
daniiee OP
Apr ’23

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?

0
bboy_creative OP
Apr ’23

This issue still persists today.

0
stoickeyboard OP
Apr ’23

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;

0
talhayavcin OP
Apr ’23

please fix this issue!

0
gr4h4m OP
Apr ’23
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.

18
EAS build is failing since today's scheduled maintenance
First post date Last post date
 
 
Q