Authentication with Apple Developer Portal failed!

[ekorman]

Build/Submit details page URL

No response

Summary

I get the error

Authentication with Apple Developer Portal failed!
Cookie not in this host's domain. Cookie:developer-mdn.apple.com Request:developer.apple.com
    Error: build command failed.

when running eas build --profile preview --platform ios. this command worked successfully a few days ago

Managed or bare?

managed

Environment

  expo-env-info 1.2.0 environment info:
    System:
      OS: macOS 14.2.1
      Shell: 5.9 - /bin/zsh
    Binaries:
      Node: 16.20.0 - ~/.nvm/versions/node/v16.20.0/bin/node
      Yarn: 1.22.19 - ~/.nvm/versions/node/v16.20.0/bin/yarn
      npm: 8.19.4 - ~/.nvm/versions/node/v16.20.0/bin/npm
      Watchman: 2023.10.30.00 - /opt/homebrew/bin/watchman
    SDKs:
      iOS SDK:
        Platforms: DriverKit 23.2, iOS 17.2, macOS 14.2, tvOS 17.2, visionOS 1.0, watchOS 10.2
    IDEs:
      Xcode: 15.2/15C500b - /usr/bin/xcodebuild
    npmPackages:
      @expo/webpack-config: ^19.0.0 => 19.0.0 
      expo: ~49.0.15 => 49.0.18 
      react: 18.2.0 => 18.2.0 
      react-dom: 18.2.0 => 18.2.0 
      react-native: 0.72.6 => 0.72.6 
      react-native-web: ~0.19.6 => 0.19.9 
    npmGlobalPackages:
      eas-cli: 7.1.3
    Expo Workflow: managed

✔ Check Expo config for common issues
✔ Check package.json for common issues
✔ Check dependencies for packages that should not be installed directly
✔ Check for common project setup issues
✔ Check for issues with metro config
✔ Check npm/ yarn versions
✔ Check Expo config (app.json/ app.config.js) schema
✔ Check that packages match versions required by installed Expo SDK
✔ Check for legacy global CLI installed locally
✔ Check that native modules do not use incompatible support packages
✔ Check that native modules use compatible support package versions for installed Expo SDK

Didn't find any issues with the project!

Error output

Authentication with Apple Developer Portal failed!
Cookie not in this host's domain. Cookie:developer-mdn.apple.com Request:developer.apple.com
Error: Cookie not in this host's domain. Cookie:developer-mdn.apple.com Request:developer.apple.com
    at M.setCookie (/Users/eric/.nvm/versions/node/v16.20.0/lib/node_modules/eas-cli/node_modules/@expo/apple-utils/build/index.js:1:927590)
    at M.setCookie (/Users/eric/.nvm/versions/node/v16.20.0/lib/node_modules/eas-cli/node_modules/@expo/apple-utils/build/index.js:1:697286)
    at /Users/eric/.nvm/versions/node/v16.20.0/lib/node_modules/eas-cli/node_modules/@expo/apple-utils/build/index.js:1:894766
    at new Promise (<anonymous>)
    at /Users/eric/.nvm/versions/node/v16.20.0/lib/node_modules/eas-cli/node_modules/@expo/apple-utils/build/index.js:1:894571
    at Object.apply (/Users/eric/.nvm/versions/node/v16.20.0/lib/node_modules/eas-cli/node_modules/@expo/apple-utils/build/index.js:1:895502)
    at /Users/eric/.nvm/versions/node/v16.20.0/lib/node_modules/eas-cli/node_modules/@expo/apple-utils/build/index.js:1:868909
    at Array.forEach (<anonymous>)
    at c (/Users/eric/.nvm/versions/node/v16.20.0/lib/node_modules/eas-cli/node_modules/@expo/apple-utils/build/index.js:1:868881)
    at /Users/eric/.nvm/versions/node/v16.20.0/lib/node_modules/eas-cli/node_modules/@expo/apple-utils/build/index.js:1:867223
    Error: build command failed.

Reproducible demo or steps to reproduce from a blank project

Run

eas build --profile preview --platform ios

[Niravpatel129]

+1 having this issue too

[alantvu]

also having this issue

[baristikir]

I'm facing the same issue stated here, builds for ios platform were working fine a few days ago but are breaking today all of sudden...

[mthomas100]

Suddenly having this issue too when running eas build --profile development --platform ios

[vbpns]

+1

[afsadilson]

++1

[frechg]

+1, Building with no issues yesterday.

[diegosilvadigital]

+1

[timohaver]

+1

EAS CLI 7.1.3 environment info:
    System:
      OS: macOS 14.3.1
      Shell: 5.9 - /bin/zsh
    Binaries:
      Node: 20.11.0 - ~/.nvm/versions/node/v20.11.0/bin/node
      npm: 10.4.0 - ~/.nvm/versions/node/v20.11.0/bin/npm
    Utilities:
      Git: 2.39.3 - /usr/bin/git
    npmPackages:
      expo: ~50.0.5 => 50.0.6 
      expo-dev-client: ~3.3.8 => 3.3.8 
      react: 18.2.0 => 18.2.0 
      react-native: 0.73.4 => 0.73.4 
    npmGlobalPackages:
      eas-cli: 7.1.3
    Project workflow: managed

[Jonatthu]

Same here with latest eas-cli

[AmitayCohen1]

Same

[strbavaclav]

+1

[hassanzeaiter]

Same

[awwbaw3]

Same

[mikeRChambers610]

+1

[lukas-sitkauskas]

+1

[vitor-rmcosta]

Same here

[MaheshtheDev]

I am facing same issue too all of the sudden!

[danielgolan]

+1

[meerbex]

Having the same issue,
There was no issue yesterday, it appeared today only!!

[druckhead]

Having the same issue

[export-mike]

same here +1

[MariuzM]

Same, was working fine 2 days ago
eas-cli/7.1.3 darwin-arm64 node-v20.11.0

So looks like nothing works when you need to build either in preview or production, once it needs that communication with apple error comes up. Feels like Apple changed something because older versions of eas is same issue.

[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]

thanks, we will investigate this.

you can use eas build --non-interactive to skip the apple auth prompt and used stored app signing credentials to work around this issue for now.

i'll lock the issue for now so that this comment is easily discoverable, and we'll follow up shortly.

[rahulraoe]

npm install -g eas-cli
Run this and the cli will be upgraded to 7.3 and that will fix the issue.

[maxsl89]

npm install -g eas-cli

helped!

[Peek-A-Booo]

I was getting the same error. I ran npm install -g eas-cli and that fixed the issue

Thanks!

[emrahyurttutan]

thanks, we will investigate this.

you can use eas build --non-interactive to skip the apple auth prompt and used stored app signing credentials to work around this issue for now.

i'll lock the issue for now so that this comment is easily discoverable, and we'll follow up shortly.

Thanks! @brentvatne @maufernandezdev

[Rico00121]

thanks, we will investigate this.
you can use eas build --non-interactive to skip the apple auth prompt and used stored app signing credentials to work around this issue for now.
i'll lock the issue for now so that this comment is easily discoverable, and we'll follow up shortly.

Thanks! @brentvatne @maufernandezdev

This worked for me! thanks! plz fix this bug ASAP : )

[ahmdshrif]

npm uninstall -g eas-cli
npm install -g eas-cli

this is work for me .

[123epsilon]

Running npm install -g eas-cli worked for me, does anyone know why this occurs?

[w8ze-devel]

Uninstalling & re installing eas-cli (thus installing version 7.3) worked for me too.

[bitcoinbrisbane]

i fixed by updating eas.json

nvm use 18.17.1
npm install -g eas-cli

{
  "cli": {
    "version": "7.3.0"
  },

[pradelkai]

Updating the cli is confirmed working on my end.

[iAhtasham]

I am still getting this error on version eas cli 7.3.0,
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.

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.

[sendaimono]

I am still getting this error on version eas cli 7.3.0, 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.

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.

upgrade to 7.5.0

[Ty-HA]

Hello
I got exactly same problem and I can't upgrade to eas 7.6.2, even after uninstall it, I did these
npm uninstall -g eas-cli
npm cache clean --force
npm install -g eas-cli

But I always got these:
$ eas --version
★ [email protected] is now available.
To upgrade, run npm install -g eas-cli.
Proceeding with outdated version.

eas-cli/7.3.0 win32-x64 node-v18.17.1

I am stucked with 7.3.0 why ?

I can't build ios "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."

[jadbadran]

Hi guys, I had the same issue, and the only thing that made it work (in my scenario) was doing eas login and logging in my Expo account before logging in my Apple Developer Account on eas build --profile preview --platform ios or in my case, it was eas device:create. Hope it worked on your ends. Good luck!

[ismoiliy98]

Version: 12.5.3
Getting the same issue.

✖ Logging in...
Authentication with Apple Developer Portal failed!
Received an internal server error from Apple's App Store Connect / Developer Portal servers, please try again later
    Error: build command failed.

Why does this error happen? Is it on Apple's side or Expo? Isn't there a way to fix it so it will not happen again in new versions?

[guifischer]

Version: 12.5.3

Same issue here. Any ideas how to fix it? Happening on build and submit for Apple

[affcue25]

Same issue Im receiving since today. It was working fine before.

Authentication with Apple Developer Portal failed! Received an internal server error from Apple's App Store Connect / Developer Portal servers, please try again later Error: build command failed.

[AroundTheWorld131]

Facing the same problem! [email protected]

EDIT:
This works for me(skips the apple auth prompt): eas build -p ios --non-interactive

[billysyt]

Received an internal server error from Apple's App Store Connect / Developer Portal servers, please try again later
Error: build command failed.

I keep reverting my code and tried so much still no luck. It's in a sudden.

[Jean-EmmanuelP]

+1

[Zakisb]

Still same issue !

[bhappen]

Same issue was occurring on eas build --platform ios as well as eas submit --platform ios. Updated to [email protected] and issue is resolved. Try running npm i -g eas-cli

[CllDMR-ekonobi]

Same issue was occurring on eas build --platform ios as well as eas submit --platform ios. Updated to [email protected] and issue is resolved. Try running npm i -g eas-cli

Worked for me. Thanks @bhappen

+UP

[Seanmclem]

the current recommendation is to use npx eas, not install eas-cli. Or do I have that wrong

[lucksp]

the current recommendation is to use npx eas, not install eas-cli. Or do I have that wrong

This is the only solution that worked for me

[CalvinNFT]

Facing the same issue here, started when I set the eas.json distribution property:

  "build": {
    "device": {
      "developmentClient": true,
      "distribution": "internal",
      "ios" : {
        "simulator": false
      }
    },
  }

when distribution is set off, problem resolves itself. And yes, I have my iPhone set on developer mode previously had no issues and even has worked with ad-hoc siz months ago. Anyway, I was able to solve my build issue by removing the distribution key:

  "build": {
    "device": {
      "developmentClient": true,
      "ios" : {
        "simulator": false
      }
    },
  }

My build command is 'npx eas build -p ios --profile device --local' (I use --local for development and our company uses our own infra to build with --local in CI instead of using Expo's cloud builds).

For me the only reason I wanted to distribute was to do ad hoc for my device, but I ended up just crying and doing it through .ipa and Apple Configurator for fast iteration and Testflight for QA and Canary.

[brentvatne]

@CalvinNFT - is your apple account the owner of the apple developer team? or what permissions does it have?

[cognitivestream]

I asked expo support and their answer was:

It appears that this issue is currently being discussed within the community, and you can find more information and potential workarounds in this thread: #2224

This is an old issue and I don't see any expo devs talking about:

• Is the root cause of this identified
• Is anyone working on fixing the problem?
• When can we expect a fix=

Instead we get "see if the community has figured out a workaround, or else just dont use our product (which you paid for and build your pipelines around)".

Expo team: Can you do better than that?

[brentvatne]

hi @cognitivestream,

The challenge here is that there are a variety of possible ways for this generic error to occur, and many of them are opaque to consumers of this API such as EAS. For example, Apple occasionally changes its endpoints without notice and we then adapt to that by releasing a new version of EAS CLI. However, some folks have slightly incorrect Node installations on their machines, which results in workarounds like having to run npx eas-cli instead of eas because they are unable to replace an existing eas-cli installation with the latest version. This is not an EAS CLI issue, in this case developers should troubleshoot their Node installation to determine why npm i -g eas-cli followed by eas does not give the latest version, but npx eas-cli does. (for example: #2224 (comment))

You mentioned that you do not see any feedback from Expo developers, but if you expand the comments you will see that I responded: #2224 (comment)

Commenting on a closed issue is generally not helpful. If you create a new issue where you explain what you are encountering and provide any information that folks would need to help you, then you are far more likely to get help. It's quite possible that you are having the same issue as I referred to above, but you have not verified whether you are in fact actually using the correct EAS CLI version - you can run eas --version to very or run npx eas-cli@latest to ensure that is what is being used. If you'd like to share more information to help debug, you can run this: EXPO_APP_STORE_DEBUG=1 eas build -p ios. Hopefully the above advice resolves your issue, if not then I look forward to reading a followup email or a new issue with more information that we can use to help get to the bottom of it!