-
Notifications
You must be signed in to change notification settings - Fork 101
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
Authentication with Apple Developer Portal failed! [Error -36607] #1714
Comments
note: I know that this closed issue exists, but I think this is a different error |
Hello, |
fwiw, you can bypass this problem by
|
Got the same error too! ✖ Logging in...
Authentication with Apple Developer Portal failed!
Error: Apple Service Error -20209. This Apple ID has been locked for security reasons. Visit iForgot to reset your account
(https://iforgot.apple.com) EDIT: |
Maybe it's related to my specific environment, or I'm doing something wrong. |
I got this too @miran248, had to change apple password to unlock, then got the previous error back |
@anubra266 Try again, and try what @MaxAst suggested above.
|
@miran248 I run into the same sit |
I got this.. eas build --auto-submit --profile sandbox --platform ios
Specified value for "ios.bundleIdentifier" in app.config.js or app.json is ignored because an ios directory was detected in the project.
EAS Build will use the value found in the native code.
✔ 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? … no
No problem! 👌 If any of the next steps will require Apple account access we will ask you again about it.
Skipping Distribution Certificate validation on Apple Servers because we aren't authenticated.
Skipping Provisioning Profile validation on Apple Servers because we aren't authenticated.
Project Credentials Configuration
... Which version are you using? ➜ eas -v
eas-cli/3.7.0 darwin-x64 node-v19.1.0 |
eas -v |
@GiovanniFerrara No idea.. Could it be the node version? Maybe it's the operating system. I'm on macos 12.6 (monterey), mbp 13 2020 intel |
Same problem here |
Same problem here. eas-cli/3.7.0 darwin-arm64 node-v18.14.2 |
I am getting this error too. As it previously worked without a cli version change, one assumes the issue is on the Apple/Expo auth side. I believe this is a sit and wait for Expo to resolve now. FWIW to others coming across this issue. Don't keep trying, as it'll lock your Apple account and you'll have to reset your password. Edit: Tagging @EvanBacon as he dealt with a similar previous issue. |
Same problem here. |
It seems that trying to use
Looks like |
Downgrading to v3.6 gave the same error. It's worth noting that while I received the |
this same issue is occurring on fastlane: fastlane/fastlane#21072 |
Thank you for filing this issue! |
I'm investigating now, need to confirm the new endpoints. Update:I can reproduce certain authentication errors, specifically this rate limiting error:
But authentication sometimes works in https://idmsa.apple.com/signin (then timesout instantly). I think Apple may be having some server issues at the moment. I have been able to get EAS CLI authentication working one time a moment ago (using an sms-2fa account) but then it went back to the rate limit issue. I get the same issue using |
Ok, I think I got it. Pushing a new version now. Apple appears to be locking accounts using legacy headers, after unlocking your account the new system should work as expected. The issue wasn't related to 2-Factor Authentication so if you get to the 2FA prompt and it fails, then you have encountered a different issue. |
Just updated to [email protected], but I still get an error: This error is different than the one I was receiving this morning, which had the -36607 error code in the error string. I'm on MacOS, Apple M1 Pro, running Ventura 13.2.1. |
I am also getting the error that @audieleon posted ☝️ |
Waited a few hours before retrying in case it was a rate limit issue but still getting the same result. Also tried
|
Im also experiencing the same error after upgrading to [email protected] |
What can I do to help you reproduce? |
I think I fixed it, please pull the branch for #1719 test it locally and let me know if it works! Edit: My latest PR appears to definitively solve the |
This seems to have worked, was able to login with 2fa and starting a build. Thank you @EvanBacon |
🚀 Fix is now published in |
works like a charm! Thanks a lot for the effort @EvanBacon, @brentvatne, and the rest of the expo team! |
Thank you very much, now it works |
I can confirm [email protected] works fine. Thanks everyone |
It's working with the fix. [email protected]. Thanks |
Yep, Using [email protected] is working fine! |
Working as usual with [email protected] Thanks!~ <3 |
This fixed it! Thank you @EvanBacon. |
3.7.2 is working for us. Thanks for the quick fix. |
great persistence on this @EvanBacon & @brentvatne ... product worth paying for 💰 |
it worked for me after upgrade to 3.7.2 |
This new version ( |
Tried again this morning after leaving it alone all night. I initially tried with 3.7.1, forgetting to update eas-cli, and of course that failed. However everything worked after updating to 3.7.2 without waiting between these two attempts any longer than it took to update eas-cli. Thanks for the fix! |
Yes it's working now ! Can log in and build ! Thanks to the Expo Team GG @EvanBacon @brentvatne |
i am still facing Authentication with Apple Developer Portal failed! my eas.json "cli": { "eas-cli": "^3.7.2", |
I've updated to eas-cli 3.7.2 but still face the authentication issue, regardless if I select "to log in to my Apple account" or not. |
@hazirmagron have you deleted the cache before trying? |
Hello, I have to have a paid Apple Developer account to build locally with |
After having 'eas update' installed and 'eas update --branch preview --message "try first updating" ' excuted, I don't see my app on my ios device udpated. (The ios app was installed through testflight.)
|
Build/Submit details page URL
No response
Summary
When running
eas build -p ios --auto-submit
and chooseyes
when being asked to log in to my Apple account, I get this error:after getting the error, I do get the Apple ID verification code prompt on my apple devices though, so it might be that the CLI is not able to handle cases where 2fa is required.
eas-cli/3.6.1 darwin-arm64 node-v18.12.1
Managed or bare?
managed
Environment
expo-env-info 1.0.5 environment info:
System:
OS: macOS 13.2
Shell: 5.8.1 - /bin/zsh
Binaries:
Node: 18.12.1 - ~/.nvm/versions/node/v18.12.1/bin/node
Yarn: 1.22.19 - ~/.yarn/bin/yarn
npm: 8.19.2 - ~/.nvm/versions/node/v18.12.1/bin/npm
Watchman: 2023.02.13.00 - /opt/homebrew/bin/watchman
Managers:
CocoaPods: 1.11.3 - /opt/homebrew/bin/pod
SDKs:
iOS SDK:
Platforms: DriverKit 22.2, iOS 16.2, macOS 13.1, tvOS 16.1, watchOS 9.1
IDEs:
Xcode: 14.2/14C18 - /usr/bin/xcodebuild
npmGlobalPackages:
eas-cli: 3.6.1
expo-cli: 6.3.0
Expo Workflow: managed
Error output
Authentication with Apple Developer Portal failed!
Error: Apple Service Error -36607. Unable to sign you in to your Apple ID. Try again later. Learn more. Opens in a new window.
Reproducible demo or steps to reproduce from a blank project
eas build -p ios --auto-submit
The text was updated successfully, but these errors were encountered: