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

@Oskya from the discord channel gave me a hint that builds without login works, I tried and it is building now

Just try selecting no for the Do you want to login question

Update: run npm install -g eas-cli for the definitive solution.

SUPER dirty workaround!

1. Find where your eas-cli located (For me its /usr/local/lib/node_modules/eas-cli)
2. Open file node_modules/@expo/apple-utils/build/index.js
3. Find 2 strings (use find tool in your ide): ignoreError:r.ignoreCookieErrors and replace to ignoreError:true
4. Done!

Updating eas cli version fixed the problem

Updating my eas-cli to version 3.5.2 fixed the issue.

We are aware of the issue, and are currently investigating it. Keep an eye on our status page for updates: https://status.expo.dev/incidents/thkksr16ctcr?u=3m49hn47l584

Upgrading to eas-cli 3.5.2 fixed this for me.

npm install -g eas-cli

after updating eas cli to 3.5.2 build and submit worked

We’re monitoring the situation after the release of eas-cli@3.5.2. If you run into any new issues after installing the new eas-cli version, please report them here. Thank you for your patience!

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

npm install -g eas-cli

and it supposed to work

I had the same issue

Updating my eas-cli version solved it for me.

npm install -g eas-cli

Had same issue Upgrading to 3.5.2 solved my issue as well npm install -g eas-cli

I also have been hitting the same issue with the latest. Temporary workaround is to go back to older version. Uninstall the latest version and install this version. npm install -g eas-cli@3.7.2

Make sure to update to eas.json file "version": "3.7.2", too. It was causing my errors.

I also have been hitting the same issue with the latest. Temporary workaround is to go back to older version. Uninstall the latest version and install this version. npm install -g eas-cli@3.7.2

eas-cli update fixed the problem.

Quick fix that worked for me ✔ Do you want to log in to your Apple account? … y/n Just hit No on this step.

Issue is back, npm install -g eas-cli@latest not helping.

version: eas-cli/7.1.3 darwin-arm64 node-v20.9.0

Im getting the same issue too. You can start build without the login option, but it continues if you try uploading your build to store.

Me too, I’m currently having this problem for the first time eas-cli@7.1.3 darwin-arm64 node-v20.9.0

✔ Logged in New session Authentication with Apple Developer Portal failed! Cookie not in this host’s domain. Cookie:developer-mdn.apple.com Request:developer.apple.com

I am also having the same issue. Installing latest CLI doesnt work and selecting no to logging in also does not work.

Issue is back, npm install -g eas-cli@latest not helping.

I am having his issue for the first time now too

@opeah solution worked for me!!

(remove) yarn global remove eas-cli

(re-install) yarn add remove eas-cli

Me too, I’m currently having this problem for the first time eas-cli@7.1.3 darwin-arm64 node-v20.9.0

✔ Logged in New session Authentication with Apple Developer Portal failed! Cookie not in this host’s domain. Cookie:developer-mdn.apple.com Request:developer.apple.com

I think I found a temporary solution to this problem.

• Use the command ‘eas build --platform ios --clear-cache’

• When it asks you ‘√ Do you want to log in to your Apple account?’ Press Y to log into your account.

• When the error appears, enter the link of your files (The underlined with green in the image down), when you enter that file (cookie.json or something like that), delete everything that appears there, don’t worry, now we will solve that.

• Now use again the command ‘eas build --platform ios --clear-cache’

• When it asks you ‘√ Do you want to log in to your Apple account?’ Press N to not log into your account.

• With the command like that it will automatically fill everything we deleted in the cookie.json file in an updated way.

• Then will create the .ipa file normally, then use ‘eas submit -p ios --latest’ to upload it to AppStoreConnect.

It worked normal for me when I created it this way without any more problems. Until they resolve the issue it may be a temporary solution.

@audieleon try changing keyPassword to password

I was able to get it to build successfully using local credentials.

npm install -g eas-cli

This fixed my case, too.

I’m still seeing the cookie error after updating to 3.5.2 when using the credential manager. I’ve tried just about all of the different options and they all seem to have the same results. I am trying to update a push notification cert that is expiring tomorrow.

The new version with the fix from @brentvatne, 3.5.2, was just released. Updated it and it’s now working as expected!

The older 3.7.2 version passes the login but it doesn’t seem to support the ENV vars, I have a different APP ID for the staging version, so it doesn’t work for me. 😔

I also have been hitting the same issue with the latest. Temporary workaround is to go back to older version. Uninstall the latest version and install this version. npm install -g eas-cli@3.7.2

Worked for me, thank you! I was on eas-cli/7.1.3 darwin-arm64 node-v20.11.0 when it didnt work for me.

Same problem for me with exactly the same text as above. On eas-cli version 7.1.2.

Selecting no to login allowed the build to continue successfully in this case.

Seems there’s more going on that just this Cookie issue. Everyone just needs to upgrade to the latest version of eas-cli - its that easy.

See: #1714 And: https://status.expo.dev/incidents/lzbndzp3ql1z

Install `eas-cli@3.7.2` with `npm i -g eas-cli` and re-run your build/submission if you encountered this issue.
Posted 25 minutes ago. Feb 24, 2023 - 09:25 PST

Just upgrading for me didn’t work (even with 3.6.0). I had to remove it completely and reinstall, now it works.

Upgrading eas-cli version fixed the problem for me too

npm install -g eas-cli

We’re considering the issue resolved. Please open a new issue for any new issues you might encounter.

Just build your app without ios login. and add this your eas.json

"submit": {
    "production": {
      "ios": {
        "appleId": "email@email.com",
        "ascAppId": "[Your app id]"
      }
    }
  }

then;

eas submit --platform ios

And your submit is OK! That’s it!

@eirikhanasand There are two occurrences, be sure to replace them both and save the file! I did, unfortunately having no luck with this…

SUPER dirty workaround!

1. Find where your eas-cli located (For me its /usr/local/lib/node_modules/eas-cli)
2. Open file node_modules/@expo/apple-utils/build/index.js
3. Find 2 strings (use find tool in your ide): ignoreError:r.ignoreCookieErrors and replace to ignoreError:true
4. Done!

Yes, its worked! My windows path: C:\Users\User\AppData\Roaming\npm\node_modules\eas-cli\node_modules\@expo\apple-utils\build

The solution I’m using is selecting ‘no’ when prompted to login to the Apple account, and then uploading the build manually with xcrun altool --upload-app -f <PathToFile>.ipa -u <Username> -p <Password>.

This worked for me after doing eas build --platform ios you get a link to your .ipa that you can get and download

I also had to pass --type ios along with creating an app specific password https://appleid.apple.com/ .

Said no to login, download the ipa file, use transporter to upload the file, seems to work.

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

Eu também tenho encontrado o mesmo problema com o mais recente. A solução temporária é voltar para a versão mais antiga. Desinstale a versão mais recente e instale esta versão. npm instalar -g eas-cli@3.7.2

Boa, resolveu aqui pra mim também!

meu eas.json tá assim

"cli": {
    "version": ">= 0.56.0"
  }

I also have been hitting the same issue with the latest. Temporary workaround is to go back to older version. Uninstall the latest version and install this version. npm install -g eas-cli@3.7.2

Great temporary solution for me as well

I also have been hitting the same issue with the latest. Temporary workaround is to go back to older version. Uninstall the latest version and install this version. npm install -g eas-cli@3.7.2

Thanks you so much, worked for me too. Got my build on App store connect and about to submit app for review. This issue will probably get fixed in a day or two and update to the newest version will take care of it, but I am in a time crunch so I can’t wait. Thanks for the solution again, you saved me a good amount of stress.

Same issue +1

@opeah solution worked for me!! (remove) yarn global remove eas-cli (re-install) yarn add remove eas-cli

Might want to update your re-install command, but removing with yarn worked for me when running the npm command to install the new version of eas-cli wasn’t working.

Worked for me!

We are aware of the issue, and are currently investigating it. Keep an eye on our status page for updates: https://status.expo.dev/incidents/thkksr16ctcr?u=3m49hn47l584

updating to eas-cli worked.

I used this command: sudo npm install --global eas-cli --force sudo because of my permission/access on mac and force because it already existed so it threw an error. Then i tried building again and it worked at the log in step (which it didnt before updating eas-cli)

Quick fix that worked for me ✔ Do you want to log in to your Apple account? … y/n Just hit No on this step.

This worked for me when running eas build --platform ios, but not with eas submit --platform ios --latest. Adding ascAppId to eas.json made eas submit work for me. Guide for ascAppId here

Works for me as well 👍🏼 Thanks

Sumbmission is not working too

SUPER dirty workaround!

1. Find where your eas-cli located (For me its `/usr/local/lib/node_modules/eas-cli`)

2. Open file `node_modules/@expo/apple-utils/build/index.js`

3. Find 2 strings (use find tool in your ide): `ignoreError:r.ignoreCookieErrors` and replace to `ignoreError:true`

4. Done!

This let me go through the first step, but then when generating new app store connect api key it fails again.

Quick fix that worked for me ✔ Do you want to log in to your Apple account? … y/n Just hit No on this step.

This worked for me when running eas build --platform ios, but not with eas submit --platform ios --latest. Adding ascAppId to eas.json made eas submit work for me. Guide for ascAppId here

Hi, I am also following this issue right now, and I went to https://github.com/expo/eas-cli/issues/1672#issuecomment-1416940702 and was able to build, but I am having trouble submitting. I am having trouble submitting. Has anyone solved this problem?

After eas built the .ipa, I was similarly not able to use eas submit. So I used the command line

xcrun altool --upload-app -f ~/Downloads/application-xxxxx.ipa -t ios -u appleDevEmail@x.com -p aaaa-aaaa-aaaa-aaaa

For the password i went here and created an app specific password https://appleid.apple.com/account/manage

@audieleon try changing keyPassword to password

I was able to get it to build successfully using local credentials.

Build is going now. Thank you.

anyone on a mac can use local credentials https://docs.expo.dev/app-signing/local-credentials/

Edit: This is also getting “ARCHIVE FAILED” as commented below.

Thanks for the suggestion. Had high hopes for this. Set up the certs exactly as specified, and I got this result:

The contents of my credentials.json are

{
  "ios": {
    "provisioningProfilePath": "ios/certs/AudieSheridanZeroProvisioning.mobileprovision",
    "distributionCertificate": {
      "path": "ios/certs/AudieSheridanZeroDev.p12",
      "keyPassword": "<password>"
    }
  }
}

Anyone seen this before?

anyone on a mac can use local credentials https://docs.expo.dev/app-signing/local-credentials/

Edit: Removed error, this is working for others.

same issue