Authentication with Apple Developer Portal failed! [Error -36607] #1714

MaxAst · 2023-02-23T09:49:44Z

Build/Submit details page URL

No response

Summary

When running eas build -p ios --auto-submit and choose yes when being asked to log in to my Apple account, I get this error:

✖ Logging in...
Authentication with Apple Developer Portal failed!
    Error: Apple Service Error -36607. Unable to sign you in to your Apple ID. Try again later. <a target="_blank" 
    href="https://support.apple.com/kb/HT212522 ">Learn more.<span class="sr-only"> Opens in a new window.</span></a>

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:

MaxAst · 2023-02-23T09:50:31Z

note: I know that this closed issue exists, but I think this is a different error

AChevallier · 2023-02-23T10:00:10Z

Hello,
I do have the same problem!

MaxAst · 2023-02-23T10:14:58Z

fwiw, you can bypass this problem by

choosing no when being asked to log in to your Apple account
download the build's .ipa file from your expo dashboard
submit the .ipa file to App Store Connect via Transporter

miran248 · 2023-02-23T12:09:20Z

Got the same error too!
And me being who i am, i ran it twice and got a different error the second time :)

✖ 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:
I later ran it again and got the error 36607 again.
After that i ran it again, this time choosing no and this time i had no issues; what's more, a few minutes later i got an email from testflight, saying the app was now available to test.

GiovanniFerrara · 2023-02-23T12:49:30Z

Maybe it's related to my specific environment, or I'm doing something wrong.
When I select "no" when being asked to log in to my Apple account I get the question about my credentials again.

anubra266 · 2023-02-23T12:59:25Z

Got the same error too! And me being who i am, i ran it twice and got a different error the second time :)
✖ 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)

I got this too @miran248, had to change apple password to unlock, then got the previous error back

miran248 · 2023-02-23T13:02:57Z

@anubra266 Try again, and try what @MaxAst suggested above.

fwiw, you can bypass this problem by

choosing no when being asked to log in to your Apple account

download the build's .ipa file from your expo dashboard

submit the .ipa file to App Store Connect via Transporter

anubra266 · 2023-02-23T13:05:39Z

@anubra266 Try again, and try what @MaxAst suggested above.

fwiw, you can bypass this problem by

choosing no when being asked to log in to your Apple account

download the build's .ipa file from your expo dashboard

submit the .ipa file to App Store Connect via Transporter

@miran248 I run into the same sit

uation as @GiovanniFerrara

miran248 · 2023-02-23T13:09:51Z

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

GiovanniFerrara · 2023-02-23T13:11:16Z

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
eas-cli/3.7.0 darwin-arm64 node-v14.20.1

miran248 · 2023-02-23T13:17:19Z

@GiovanniFerrara No idea.. Could it be the node version?
eas-cli uses node 18 it seems. Not sure how much that's playing a role.

Maybe it's the operating system. I'm on macos 12.6 (monterey), mbp 13 2020 intel

AdminGrupoZoe · 2023-02-23T13:23:42Z

Same problem here

ilgiapa · 2023-02-23T13:36:10Z

Same problem here.

eas-cli/3.7.0 darwin-arm64 node-v18.14.2

SamPoate · 2023-02-23T13:46:01Z

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.

GKyomen · 2023-02-23T13:55:27Z

Same problem here.
eas-cli/3.7.0 darwin-x64 node-v18.14.0
Also tried in Mac, Windows and Ubuntu, all those failed.

d4rky-pl · 2023-02-23T15:14:07Z

It seems that trying to use eas right now and logging in to your Apple account more than once results in a soft lock of the account. I had to log back in on my Mac after trying and change my password because

Your Apple ID has been locked for security reasons. To unlock it, you must verify your identity.

Looks like eas device:create, eas submit etc. are all affected

shaneboyar · 2023-02-23T16:22:07Z

Downgrading to v3.6 gave the same error. It's worth noting that while I received the Authentication with Apple Developer Portal failed! error in the cli. A 2FA code was pushed to my physical device. Its almost as if the CLI just isnt waiting for the 2FA process.

brentvatne · 2023-02-23T17:18:01Z

this same issue is occurring on fastlane: fastlane/fastlane#21072
it looks like Apple changed an API without notice. we're going to update for this as soon as possible. for now, indeed, you can skip the authentication part

expo-bot · 2023-02-23T17:18:20Z

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.

EvanBacon · 2023-02-23T17:46:48Z

I'm investigating now, need to confirm the new endpoints.

Update:

I can reproduce certain authentication errors, specifically this rate limiting error:

> Request: https://idmsa.apple.com/appleauth/auth/signin
> Response:
Apple Service Error -36607. Unable to sign you in to your Apple ID. Try again later. <a target="_blank" href="https://support.apple.com/kb/HT212522 ">Learn more.<span class="sr-only"> Opens in a new window.</span></a>

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 fastlane spaceauth. Going to try adjusting the cookies to see if that helps. FYI, this Fastlane PR only appears to update 2fa device codes using the legacy four digit codes, most people aren't using this.

EvanBacon · 2023-02-23T20:59:34Z

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.

audieleon · 2023-02-24T05:51:42Z

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.

rawestmoreland · 2023-02-24T06:25:44Z

I am also getting the error that @audieleon posted ☝️

garyThrels · 2023-02-24T07:01:31Z

Waited a few hours before retrying in case it was a rate limit issue but still getting the same result. Also tried rm -rf ~/.app-store before, but nothing changed

Still getting the below error with using eas-cli/3.7.1 darwin-arm64 node-v16.17.0
✖ Logging in...
Authentication with Apple Developer Portal failed!
    Error: Apple Server Error: Unable to sign you in to your Apple ID. Try again later. The following support link is provided by Apple but it may not be 
    relevant: Learn more: https://support.apple.com/kb/HT212522
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
Also gets the apple 2fa popup. Not sure if related or as the apple error suggests, I need to wait 24hrs

flo951 · 2023-02-24T07:30:36Z

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.

Im also experiencing the same error after upgrading to [email protected]

audieleon · 2023-02-24T08:02:14Z

Cannot reliably reproduce the error after 3.7.1 but still investigating, there are a few more headers we can try emulating.

What can I do to help you reproduce?

EvanBacon · 2023-02-24T08:04:53Z

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 -36607 error. Will merge and republish.

garyThrels · 2023-02-24T08:16:27Z

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 -36607 error. Will merge and republish.

This seems to have worked, was able to login with 2fa and starting a build. Thank you @EvanBacon

EvanBacon · 2023-02-24T08:19:58Z

🚀 Fix is now published in [email protected] 🚀

MaxAst · 2023-02-24T08:36:52Z

works like a charm! Thanks a lot for the effort @EvanBacon, @brentvatne, and the rest of the expo team!

flo951 · 2023-02-24T08:39:02Z

Thank you very much, now it works

opmat · 2023-02-24T08:40:56Z

🚀 Fix is now published in [email protected] 🚀

I can confirm [email protected] works fine. Thanks everyone

franckranaivo · 2023-02-24T08:51:34Z

It's working with the fix. [email protected]. Thanks

elenitaex5 · 2023-02-24T11:50:23Z

Yep, Using [email protected] is working fine!

ioness · 2023-02-24T11:53:11Z

Working as usual with [email protected]

Thanks!~ <3

noahkurz · 2023-02-24T12:56:32Z

This fixed it! Thank you @EvanBacon.

ian · 2023-02-24T13:00:12Z

3.7.2 is working for us. Thanks for the quick fix.

67millwood · 2023-02-24T13:26:09Z

great persistence on this @EvanBacon & @brentvatne ... product worth paying for 💰

dmitryame · 2023-02-24T14:06:48Z

it worked for me after upgrade to 3.7.2

Alan-Graton · 2023-02-24T15:26:59Z

This new version (3.7.2) worked just fine for me. After updating just ran the build/submit eas command again

Alan-Graton · 2023-02-24T15:51:36Z

I am still getting the following error on 3.7.2 - do I just need to wait out the 24 hour period from Apple?

Probably, this happened to me yesterday. I had to await 24h, install this new fix and try again.

charlesfsl · 2023-02-24T15:56:12Z

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!

LouisSyfer · 2023-02-25T00:33:25Z

Yes it's working now ! Can log in and build ! Thanks to the Expo Team GG @EvanBacon @brentvatne

jayganatrate · 2023-02-25T09:07:34Z

i am still facing Authentication with Apple Developer Portal failed!
Cookie not in this host's domain. Cookie:developer-mdn.apple.com Request:developer.apple.com

my eas.json

"cli": {
"version": ">= 3.1.1",
"promptToConfigurePushNotifications": false
},
"build": {
"development": {
"ios": {
"simulator": true,
"image": "latest"
},
"android": {
"buildType": "apk"
}
},
"production": {
"ios": {
"credentialsSource":"local",
"image": "latest"
}
}
},
"submit": {
"production": {}
}
}

"eas-cli": "^3.7.2",

hazirmagron · 2023-02-28T15:50:11Z

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.

Denver-sn · 2023-03-02T23:55:26Z

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?

ahelord · 2023-04-21T03:41:10Z

Hello, I have to have a paid Apple Developer account to build locally with eas build --platform ios --local, why do I get this error?

oliverxuyong · 2024-02-13T05:44:43Z

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.)
Then I thought I might need to run the 'eas build --platform ios' again, but got the following errors (before the 'eas update' installation, this 'eas build...' was good)

MaxAst added the needs review Issue is ready to be reviewed by a maintainer label Feb 23, 2023

MaxAst changed the title ~~Authentication with Apple Developer Portal failed!~~ Authentication with Apple Developer Portal failed! [Error -36607] Feb 23, 2023

brentvatne added issue accepted and removed needs review Issue is ready to be reviewed by a maintainer labels Feb 23, 2023

brentvatne assigned EvanBacon Feb 23, 2023

brentvatne mentioned this issue Feb 23, 2023

EAS build not prompting for 2FA with Apple ID expo/expo#21364

Closed

cdosborn mentioned this issue Feb 23, 2023

Authentication with Apple Developer Portal failed! #1220

Closed

EvanBacon closed this as completed Feb 23, 2023

EvanBacon reopened this Feb 23, 2023

EvanBacon mentioned this issue Feb 24, 2023

[eas-cli] bump apple-utils to support hashcash for authentication #1719

Merged

EvanBacon closed this as completed in #1719 Feb 24, 2023

danielricecodes mentioned this issue Feb 24, 2023

Error: Cookie not in this host's domain. Cookie:developer-mdn.apple.com Request:developer.apple.com #1672

Closed

Authentication with Apple Developer Portal failed! [Error -36607] #1714

Authentication with Apple Developer Portal failed! [Error -36607] #1714

Comments

MaxAst commented Feb 23, 2023

Build/Submit details page URL

Summary

Managed or bare?

Environment

Error output

Reproducible demo or steps to reproduce from a blank project

MaxAst commented Feb 23, 2023

AChevallier commented Feb 23, 2023

MaxAst commented Feb 23, 2023

miran248 commented Feb 23, 2023 • edited Loading

GiovanniFerrara commented Feb 23, 2023

anubra266 commented Feb 23, 2023

miran248 commented Feb 23, 2023

anubra266 commented Feb 23, 2023

miran248 commented Feb 23, 2023

GiovanniFerrara commented Feb 23, 2023

miran248 commented Feb 23, 2023 • edited Loading

AdminGrupoZoe commented Feb 23, 2023

ilgiapa commented Feb 23, 2023

SamPoate commented Feb 23, 2023 • edited Loading

GKyomen commented Feb 23, 2023

d4rky-pl commented Feb 23, 2023

shaneboyar commented Feb 23, 2023

brentvatne commented Feb 23, 2023

expo-bot commented Feb 23, 2023

EvanBacon commented Feb 23, 2023 • edited Loading

Update:

EvanBacon commented Feb 23, 2023 • edited Loading

audieleon commented Feb 24, 2023 • edited Loading

rawestmoreland commented Feb 24, 2023 • edited Loading

garyThrels commented Feb 24, 2023

flo951 commented Feb 24, 2023

audieleon commented Feb 24, 2023

EvanBacon commented Feb 24, 2023 • edited Loading

garyThrels commented Feb 24, 2023 • edited Loading

EvanBacon commented Feb 24, 2023

MaxAst commented Feb 24, 2023 • edited Loading

flo951 commented Feb 24, 2023

opmat commented Feb 24, 2023 • edited Loading

franckranaivo commented Feb 24, 2023

elenitaex5 commented Feb 24, 2023

ioness commented Feb 24, 2023

noahkurz commented Feb 24, 2023

ian commented Feb 24, 2023

67millwood commented Feb 24, 2023

dmitryame commented Feb 24, 2023

Alan-Graton commented Feb 24, 2023

Alan-Graton commented Feb 24, 2023

charlesfsl commented Feb 24, 2023

LouisSyfer commented Feb 25, 2023

jayganatrate commented Feb 25, 2023

hazirmagron commented Feb 28, 2023

Denver-sn commented Mar 2, 2023

ahelord commented Apr 21, 2023

oliverxuyong commented Feb 13, 2024 • edited Loading

miran248 commented Feb 23, 2023 •

edited

Loading

miran248 commented Feb 23, 2023 •

edited

Loading

SamPoate commented Feb 23, 2023 •

edited

Loading

EvanBacon commented Feb 23, 2023 •

edited

Loading

EvanBacon commented Feb 23, 2023 •

edited

Loading

audieleon commented Feb 24, 2023 •

edited

Loading

rawestmoreland commented Feb 24, 2023 •

edited

Loading

EvanBacon commented Feb 24, 2023 •

edited

Loading

garyThrels commented Feb 24, 2023 •

edited

Loading

MaxAst commented Feb 24, 2023 •

edited

Loading

opmat commented Feb 24, 2023 •

edited

Loading

oliverxuyong commented Feb 13, 2024 •

edited

Loading