Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Authentication with Apple Developer Portal faile #187

Open
tinkerer opened this issue Dec 10, 2024 · 9 comments
Open

Authentication with Apple Developer Portal faile #187

tinkerer opened this issue Dec 10, 2024 · 9 comments

Comments

@tinkerer
Copy link

tinkerer commented Dec 10, 2024

I note that the previous issue was closed earlier today and the latest build's error points to this URL:
https://expo.fyi/apple-2fa-sms-issues-workaround.md

Internal Server Error: 'h', 'Received an internal server error from Apple's App Store Connect / Developer Portal servers, please try again later. Apple service errors:

  • Verification codes can’t be sent to this phone number at this time. Please try again later.
    If you encounter persistent issues with Apple 2FA SMS authentication, you can try using these workarounds: https://expo.fyi/apple-2fa-sms-issues-workaround.md.'. Retrying after 3 seconds (remaining: 3)

✖ 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. Apple service errors:

  • Verification codes can’t be sent to this phone number at this time. Please try again later.
    If you encounter persistent issues with Apple 2FA SMS authentication, you can try using these workarounds: https://expo.fyi/apple-2fa-sms-issues-workaround.md.
    Error: build command failed.

However, regarding the Device 2FA instructions at https://github.com/expo/fyi/blob/main/apple-2fa-sms-issues-workaround.md

I am never prompted:
How do you want to validate your account?

eas -v
eas-cli/14.1.0 darwin-arm64 node-v22.10.0
Note that I also followed the instructions in this issue (rm -rf ~/.app-store)
expo/eas-cli#2698

The issue seems to be due to the fact that I have multiple accounts with Apple, one account email is the user account on my Mac and is not the same as the developer account email at the company I am working for. This was resolved for me by signing out of my Apple Account in System Settings and signing in to the developer account. I am filing an issue to update the workaround.md file and help other developers who may be experiencing similar problems and so that expo team can update the eas-cli so that developers do not have to sign out of their personal Mac account to use a different developer account.

@arapocket
Copy link

worked for me, ty

@szdziedzic
Copy link
Member

I am never prompted:
How do you want to validate your account?

Could you clarify what we are missing in this FYI doc? Feel free to open the PR as well to change it directly 🙏

@tinkerer
Copy link
Author

I am never prompted:
How do you want to validate your account?

Could you clarify what we are missing in this FYI doc? Feel free to open the PR as well to change it directly 🙏

created a PR with the text suggested by ChatGPT (copied this thread and the original workaround.md and asking for markdown for a PR):

#189

@JSheffer-netjets
Copy link

The issue our team is running into is that our work Macs do not allow us to sign into our apple accounts so we are not actually able to set them up as trusted 2FA devices and we do not have dedicated ios work devices

@bennettfrazier
Copy link

Confirmed this fix worked for me: https://github.com/expo/fyi/blob/main/apple-2fa-sms-issues-workaround.md

  1. Run npm install -g eas-cli
  2. Run eas -v to check version. Mine was eas-cli/14.2.0
  3. Remove the app store cache. rm -rf ~/.app-store/ Note: this will log you out of Apple account stored in eas
  4. Run normal eas cli build step.. e.g.: eas build --platform ios
  5. You should be prompted to "Log in to your Apple Developer account to continue" with your Apple ID

@JSheffer-netjets
Copy link

Sorry I tried that suggestion already and it doesn't seem to make a difference. I also ensured that I am on eas-cli 14.2.0
eas-cli/14.2.0 darwin-arm64 node-v18.18.0

Here is the output when it tries to login

Screenshot 2024-12-30 at 9 26 20 AM

@ggyprodev
Copy link

Thank you, this worked for me. However I'd prefer to stay logged in to my personal account on my Mac, does the expo team have a workaround for this? Also, do they know what changed recently, as this has never been a problem before running eas build --platform ios.

@lizhensley
Copy link

lizhensley commented Feb 17, 2025

I am in the same boat – logged into my Mac with my personal account but trying to deploy using my work account. I also would like to not have to log out of my personal account on my Mac.

@ferguimara
Copy link

this worked for me! i wasn't even logged into my personal account on my mac computer but once I logged in with my business account it worked. Very strange since my build command was working last week. Thanks all

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

8 participants