Note
On 2024-11-15 it was reported that Apple API was throwing internal server errors while trying to send 2FA SMS codes for American phone numbers, when authenticating through EAS CLI. The Expo team has since updated the EAS CLI to match the new authentication requests. The issue should be fixed in version 14.0.3.
If you are experiencing persistent issues with Apple SMS 2FA while logging in through EAS CLI, you should switch to using the device 2FA method. Apple has recently changed their APIs in a way that has made this auth method less reliable for external tools (for example, see fastlane#28816). At Expo, we have adjusted our implementation to fix many cases but we do not have any direct access to the information that would allow us to feel confident that we can fix it in every scenario. For this reason, we strongly recommend moving to device 2FA instead.
We'll continue improving the SMS 2FA as best we can, and EAS CLI currently handles it better than any other tool that we are aware of, but we can't guarantee that it will be reliable. It is possible that Apple may be moving away from the SMS 2FA method, given that it is generally considered to be less secure than alternative approaches.
Follow these Apple docs to set a trusted device (for example your Mac) for your Apple account.
Once the trusted device is set up, you can use the device 2FA method when prompted How do you want to validate your account? in the EAS CLI.
This method will send a 2FA code to your trusted device, which you can then enter in the CLI to authenticate.
If you still encounter this issue while using EAS CLI version >= 14.0.3, you can try to remove old Apple authentication cache.
It seems to fix the issue for some users.
Run the following command to remove the Apple authentication cache used by EAS CLI:
rm -rf ~/.app-store/After removing the cache, try logging in again with the EAS CLI.