-
Notifications
You must be signed in to change notification settings - Fork 104
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
Comments
I'm getting the same error with eas-cli 15.0.14 |
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. |
I still got the same issue with |
Same issue here, Macbook Air, no Apple mobile |
Same here. No luck, have tried all workarounds I could find on the internet. |
Same issue here. I'm on 15.0.14 and no luck with all workarounds I can find |
Tried this morning and it's suddenly working |
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! |
It's working for me now. |
This fix worked for me as well Signed out of an IPad that was using personal credentials |
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.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:
Error output
No response
Reproducible demo or steps to reproduce from a blank project
not really a project related problem
The text was updated successfully, but these errors were encountered: