Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

eas-cli should provide instructions / alternative to "Authentication with Apple Developer Portal failed!" #2935

Open
hems opened this issue Mar 8, 2025 · 10 comments
Labels
needs review Issue is ready to be reviewed by a maintainer

Comments

@hems
Copy link

hems commented Mar 8, 2025

Build/Submit details page URL

No response

Summary

Today it's the first time I have issues building with EAS, generally I build for production and then I do an auto-submit.

This time it didn't work, potentially due to apple's own problems (related to #2143) with rate limit or perhaps it's related to the fact i have moved between a few different countries in the last days and it triggered some sort of flag on their security policies ( logging via browser works, it's just the eas build that's not working ).

Regardless of the reason, i believe eas-cli should point the user to an alternative way of building and/or submiting the build since not being able to submit a bugfix could potentially be catastrophic.

✖ Logging in...
Authentication with Apple Developer Portal failed!
Too many verification codes have been sent. Enter the last code you received or try again later.
Error: build command failed.

Managed or bare?

managed

Environment

expo-env-info 1.2.2 environment info:
System:
OS: macOS 14.4
Shell: 5.9 - /bin/zsh
Binaries:
Node: 23.6.0 - /opt/homebrew/bin/node
Yarn: 1.22.22 - /opt/homebrew/bin/yarn
npm: 10.9.2 - /opt/homebrew/bin/npm
Watchman: 2024.12.02.00 - /opt/homebrew/bin/watchman
Managers:
CocoaPods: 1.16.2 - /opt/homebrew/bin/pod
SDKs:
iOS SDK:
Platforms: DriverKit 23.5, iOS 17.5, macOS 14.5, tvOS 17.5, visionOS 1.2, watchOS 10.5
IDEs:
Android Studio: 2024.2 AI-242.23339.11.2421.12700392
Xcode: 15.4/15F31d - /usr/bin/xcodebuild
npmPackages:
expo: ^52.0.37 => 52.0.37
expo-router: ~4.0.17 => 4.0.17
react: 18.3.1 => 18.3.1
react-dom: 18.3.1 => 18.3.1
react-native: 0.76.7 => 0.76.7
react-native-web: ~0.19.13 => 0.19.13
npmGlobalPackages:
eas-cli: 14.1.0
Expo Workflow: bare


Running 15 checks on your project...
14/15 checks passed. 1 checks failed. Possible issues detected:
Use the --verbose flag to see more details about passed checks.

Advice:

  • Update React Native Directory to include metadata for unknown packages. Alternatively, set expo.doctor.reactNativeDirectoryCheck.listUnknownPackages in package.json to false to skip warnings about packages with no metadata, if the warning is not relevant.

Error output

No response

Reproducible demo or steps to reproduce from a blank project

not really a project related problem

@hems hems added the needs review Issue is ready to be reviewed by a maintainer label Mar 8, 2025
@drdpedroso
Copy link

I'm getting the same error with eas-cli 15.0.14

@HassaznAzmi
Copy link

HassaznAzmi commented Mar 10, 2025

I am also getting this today with 15.0.14. My last build was two days ago with no problem.

EDIT: What fixed this for me was running this in the terminal so it doesnt use KeyChain for the password.
EXPO_NO_KEYCHAIN=1

@drdpedroso
Copy link

I am also getting this today with 15.0.14. My last build was two days ago with no problem.

EDIT: What fixed this for me was running this in the terminal so it doesnt use KeyChain for the password. EXPO_NO_KEYCHAIN=1

I still got the same issue with EXPO_NO_KEYCHAIN=1 :(

@jose-mario-jr-fetchly
Copy link

Same issue here, Macbook Air, no Apple mobile

@pixelsaurus
Copy link

Same here. No luck, have tried all workarounds I could find on the internet.

@ayou7995
Copy link

Same issue here. I'm on 15.0.14 and no luck with all workarounds I can find

@pixelsaurus
Copy link

Tried this morning and it's suddenly working

@hems
Copy link
Author

hems commented Mar 14, 2025

it's now working for me too, but still it was a good reality-check to discover that EAS build won't work every time i try to do it being for EAS or for Apple reasons.

The most amazing outcome would be if the EAS build would notice that you're trying to submit and the process have failed so then it could fallback to explaining how to do a manual submission or how to do the build locally and then send it through the website. This would have helped me a lot and i think will help many users who might end up in this situation one way or another in the future!

@ayou7995
Copy link

It's working for me now.

@renkuna
Copy link

renkuna commented Mar 18, 2025

This fix worked for me as well

Signed out of an IPad that was using personal credentials
Signed in with the account with apple development credentials on IPad
Logged into https://account.apple.com/account/manage/section/devices and saw that the ipad is listed as a device that can be used for authentication
Ran the eas submit -p ios (I ran the build without signing in since had previously done certificates and worked fine)
At this point prompted eas prompted for me to choose device / 2factor and I chose device and was able to verify through the iPad

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs review Issue is ready to be reviewed by a maintainer
Projects
None yet
Development

No branches or pull requests

7 participants