EAS build fails at apple authentication

[sirusbaladi]

Build/Submit details page URL

No response

Summary

Running eas build --profile production --platform ios

Fails with:

Logged in New session
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.

I've updated:
npm install -g eas-cli

Managed or bare?

Managed

Environment

N/A

Error output

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.

Reproducible demo or steps to reproduce from a blank project

run eas build --profile production --platform ios

[mansmahamat]

Same for me

[OgzAkt]

+1

[ReMuSoMeGA93]

same here.

[sergeyshilin]

Same,

In the meantime, eas build --non-interactive to skip the apple auth prompt and use cached signing credentials.

[ryanSoftwareEngineer]

oh no, it's happening to me too, apple status is clear though https://developer.apple.com/system-status/

[sirusbaladi]

eas build --non-interactive

what's the difference between that command and the normal eas build?

[sergeyshilin]

what's the difference between that command and the normal eas build?

If you were able to successfully log in before, it will reuse your stored credentials instead of prompting again, and as a result, will be able to run a build.

[sirusbaladi]

what's the difference between that command and the normal eas build?

If you were able to successfully log in before, it will reuse your stored credentials instead of prompting again, and as a result, will be able to run a build.

awesome, works great but now have the same issue with trying to run: eas submit -p ios.
Any way to go around it?

edit: it can't be done unless you have a mac

[iAhtasham]

I am still facing the same issue on eas-cli/7.3.0

PS D:\Projects\React Native> eas --version
eas-cli/7.3.0 win32-x64 node-v18.15.0
PS D:\Projects\React Native> eas build --profile production --platform ios
Loaded "env" configuration for the "production" profile: no environment variables specified. Learn more: https://docs.expo.dev/build-reference/variables/
√ Using remote iOS credentials (Expo server)

If you provide your Apple account credentials we will be able to generate all necessary build credentials and fully validate them.
This is optional, but without Apple account access you will need to provide all the missing values manually and we can only run minimal validation on them.
√ Do you want to log in to your Apple account? ... yes

› Log in to your Apple Developer account to continue
√ Apple ID: ... *************
› Restoring session C:\Users*.app-store\auth*******\cookie
› Session expired Local session
› The password is only used to authenticate with Apple and never stored on EAS servers
Learn more: https://bit.ly/2VtGWhU
√ Password (for ************): ... ***************
› Saving Apple ID password to the local Keychain
Learn more: https://docs.expo.dev/distribution/security#keychain
√ Logged in New session
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.
Error: build command failed.

[pratiksvaidya]

Downgrading to 7.1.0 resolved the issue for me and I was able to both build and submit to the App Store.

npm uninstall eas-cli && npm install -g [email protected]

[ahmadtech199]

@pratiksvaidya Thank you so much, now it's working 🚀🚀🚀

[zachbwh]

@pratiksvaidya legend! thank you ❤️

[noctivityinc]

Make sure to update your eas.json file as well in case you have a constraint :)

[StephenPalazzo]

Delete your eas.json file, and rerun eas build:configure

[expo-bot]

Thank you for filing this issue!
This comment acknowledges we believe this may be a bug and there’s enough information to investigate it.
However, we can’t promise any sort of timeline for resolution. We prioritize issues based on severity, breadth of impact, and alignment with our roadmap. If you’d like to help move it more quickly, you can continue to investigate it more deeply and/or you can open a pull request that fixes the cause.

[brentvatne]

i released [email protected] with a change to use an endpoint that isn't under maintenance. we'll follow up soon with a better approach that automatically switches between endpoints as needed. install the latest version of eas-cli to resolve this issue.