Expo EAS Authentication with Apple Developer Portal failed #2881
Comments
burakgokcinarr
added
the
needs review
|
I'm afraid I have the same issue |
|
Same at my Site |
|
Can you try to edit the contents of there? |
szdziedzic
added
eas build
and removed
needs review
Such file already exists with same content. Tried changing it to |
|
I think the problem has something to do with Apple cookies. While Expo processes the “eas build ..........” commands (for iOS), Apple also provides Apple authentication and cookie management, and as far as I can see, it does user authentication successfully. But expo fails on the cookie management side. (I think there is a changing incompatibility) This situation urgently needs to be clearly resolved or clarified. I was temporarily able to provide my “production” output with the help of the following command. EAS_NO_INTERACTIVE=1 eas build --platform ios NOTE: EAS_NO_INTERACTIVE=1 This variable takes EAS Build out of interactive mode and makes the command run completely automatically. This means that Expo tries to continue without asking the user for login credentials or authentication. Hope this helps. |
|
I am having the same issue. Even EAS_NO_INTERACTIVE=1 eas build --platform ios doesn't work for me because the saved credentials were cleared. I wonder if this has something to do with Apple changing Apple Id to Apple Account. Edit: I found a workaround. I was using an app specific password previously and when I use my actual Apple password, it works. |
|
Workaround does not help in my case, because it crashes on Prepare credentials step in EAS |
|
It is a bit scary that this has been going on for so long. I hope it will be fixed by the expo as soon as possible. What is interesting is that there is no explanation about this or I may not have seen it :) We love Expo :) |
|
Yea still broken... had to hastily wire up local credentials instead 😕 Debug output for `eas credentials`doesn't say much but this is what https://expo.fyi/cryptic-error-eas advised I should do, maybe it'll be helpful as more proof it's broken: |
|
Having the same problem here, tried the same solutions to no avail. At one point I got an error stating too many verification codes had been sent, yet I never got one! Quite strange. EDIT: |
|
+1. Pinned fixed doesn't work for me. |
|
As far as I can see the situation is still the same. Yes the parameter “EAS_NO_INTERACTIVE=1 ” works for me but I don't want to use it. I keep checking the eas-cli version and there is no change. I don't know if Expo has an explanation but it is very interesting that it is not solved. Doesn't everyone have this problem ? If the answer is yes, it's even more interesting :) |
|
I finally got it to work! I followed this solution to get the option to select either device or sms. In case the post ever gets removed and people look this up in the far future, the post reads as:
Note: The Mac I did this on is signed into my personal account, it was only in Apple Music where I changed the account to the developer account. Additionally, the Macbook was setup as a trusted device for the developer account on the Apple Account website. I previously had also deleted ~/.app-store |
|
Solution with apple music does not work. Still receiving same old cookie domain mismatch error |
|
expo team please fix this is really annoying, its been going on for months now @EvanBacon no solution/workaround is working for me. I was able to build perfectly fine up until 2 weeks ago |
|
Hello everyone :) I wanted to refocus and take a look. I keep getting the error “Authentication with Apple Developer Portal failed!” in the build process for iOS. As I mentioned in previous posts, I don't want to use any parameters. This is the summary of my situation :) Now I did something like this. 1-) I upgraded eas cli to the latest version. ( eas -v => eas-cli/15.0.13 darwin-x64 node-v20.17.0 ) 2-) I ran rm -rf ~/.app-store/. 3-) Interestingly, I tried the following scenario. Previously, I added scripts like the following to my package.json file for brevity. Of course, like before, what I tried was the “npm run product-ios-build” command. The result was : Authentication with Apple Developer Portal failed! :( But I did point 2 again and this time I ran the “eas build” command directly. Very interesting ???? |
Build/Submit details page URL
No response
Summary
“Authentication with Apple Developer Portal failed!” error persists when I want to get production build for iOS in eas-cli/15.0.4.
The problem persists even though I do rm -rf ~/.app-store command.
urgent help :)
Managed or bare?
Managed
Environment
expo-env-info 1.2.2 environment info:
System:
OS: macOS 13.7
Shell: 5.9 - /bin/zsh
Binaries:
Node: 20.17.0 - /usr/local/bin/node
Yarn: 1.22.18 - /usr/local/bin/yarn
npm: 11.0.0 - /usr/local/bin/npm
Watchman: 2024.11.11.00 - /usr/local/bin/watchman
Managers:
CocoaPods: 1.16.2 - /Users/burakgokcinar/.rvm/gems/ruby-2.7.6/bin/pod
SDKs:
iOS SDK:
Platforms: DriverKit 23.2, iOS 17.2, macOS 14.2, tvOS 17.2, visionOS 1.0, watchOS 10.2
IDEs:
Android Studio: 2024.2 AI-242.23339.11.2421.12700392
Xcode: 15.2/15C500b - /usr/bin/xcodebuild
npmPackages:
expo: ~52.0.26 => 52.0.26
react: 18.3.1 => 18.3.1
react-native: 0.76.6 => 0.76.6
npmGlobalPackages:
eas-cli: 15.0.4
expo-cli: 6.3.10
Expo Workflow: managed
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: build command failed.
Reproducible demo or steps to reproduce from a blank project
eas build --profile production --platform ios
The text was updated successfully, but these errors were encountered: