CODEWITHSUNDEEP
iosreact-nativeexpoeas
Kollin Murphy
Kollin Murphy

Reputation: 724

EAS Build iOS Failure: Authentication with Apple Developer Portal failed

I'm using EAS to build my Expo app, and today I started getting this error when attempting to run an iOS build, either local or on EAS servers. I'm thinking it's an issue with Apple servers, so I'm hoping it gets fixed soon.

Output from build command:

✔ Select platform › iOS
✔ 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 /Users/.../.app-store/auth/.../cookie
› Session expired Local session
› Using password for ... from your local Keychain
  Learn more
✔ Logged in New session
Authentication with Apple Developer Portal failed!
    Error: Cookie not in this host's domain. Cookie:developer-mdn.apple.com Request:developer.apple.com

Anyone else have this problem and have any ideas on how to resolve it?

I've tried removing the stored authentication cookie and signing in again. I also tried signing in on App Store Connect to see if there was any issue with my account but I couldn't find one.

EDIT: The issue resolved itself after a few days. It was most likely a temporary issue with the EAS servers' connection to Apple.

Upvotes: 56

Views: 37109

Answers (9)

emrah yurttutan
emrah yurttutan

Reputation: 41

problem solved with eas build -p ios --non-interactive command.

https://github.com/expo/eas-cli/issues/2224

Upvotes: 4

user22123255
user22123255

Reputation: 1

when eas build --platform ios , it will ask , select no ✔ Do you want to log in to your Apple account? … no

Upvotes: 0

cengaver
cengaver

Reputation: 361

I was getting the same error. I was able to start the build, after selecting no for the "Do you want to log in to your Apple account?" question. I hope this workaround works for you.

github issue https://github.com/expo/eas-cli/issues/1672#issuecomment-1416851869

Edit: As @Dviros pointed out above, run npm install -g eas-cli for a definitive solution.

Upvotes: 11

Dustin Spengler
Dustin Spengler

Reputation: 7711

Reinstalling eas-cli globally using npm i -g eas-cli did not fix this problem for me.

I was able to fix this by updating the eas-cli package in my local project.

Update your package.json to "eas-cli": "^3.5.2", and then run npm i to reinstall.

Upvotes: 1

Dviros
Dviros

Reputation: 907

Updating the eas-cli version to version 3.5.2 fixed the problem for me. Just run the command:

npm install -g eas-cli

and it supposed to work

Upvotes: 89

Or Nakash
Or Nakash

Reputation: 3339

This is now fixed by the expo team. In order for it to work, all you have to do is update to the latest eas-cli. This should do it:

npm i -g eas-cli

Then build or submit you application to iOS.

eas build --platform ios --auto-submit

Of course you can ignore the --auto-submit.

Upvotes: 14

Christian Ledgard
Christian Ledgard

Reputation: 131

The EXPO team created an incident on there status page regarding this issue: Apple authentication error renewing certificates/profiles for EAS Build

We are currently investigating an upstream issue authenticating with Apple to renew certificates/profiles when using EAS Build.

If you are using local credentials, if you're running a non-interactive build, or if you don't need to login to Apple because your certificates/profiles are up to date, then you are unaffected by this incident.

I hope they fix it soon!

Upvotes: 1

Syed
Syed

Reputation: 33

use Transporter.

I got the same issue, but i solved it using transporter. I use eas build to upload it to expo server from there i download the app and upload it to Transporter.

Upvotes: 0

Kollin Murphy
Kollin Murphy

Reputation: 724

I was able to work around the Apple sign in by using local credentials.

https://docs.expo.dev/app-signing/local-credentials/

By going to the Expo website I was able to download the distribution certificate and provisioning profile certificate. There was also a file that had the password needed to access the distribution certificate. Then I configured the production build profile in eas.json with

...
"ios": {
  "credentialsSource": "local"
},
...

And I created a credentials.json file with

{
  "ios": {
    "provisioningProfilePath": "relative/path/to/provisioning/profile.mobileprovision",
    "distributionCertificate": {
      "path": "relative/path/to/distribution/certificate.p12",
      "password": "<MYPASSWORD>"
    }
  }
}

Then building with the normal command, it no longer prompted me to sign in to Apple. Build worked like a charm!

Upvotes: 4

Related Questions