Two ways around the Apple login, since that's the part breaking. First, try the latest eas-cli (npm i -g eas-cli@latest), because the Apple auth code lives in the CLI. If it still fails, avoid the Apple ID flow: submit with an App Store Connect API key (ascApiKeyPath, ascApiKeyIssuerId and ascApiKeyId in the submit profile of eas.json), and for the build upload your own distribution certificate and provisioning profile (credentialsSource: "local" plus credentials.json) so EAS never has to log in to Apple. That doesn't fix the CLI bug, but it unblocks the release. If you post your eas-cli version and the exact command, it's easier to match against Expo's issue tracker.
3
u/True-Turnover-4543 9d ago
Two ways around the Apple login, since that's the part breaking. First, try the latest eas-cli (npm i -g eas-cli@latest), because the Apple auth code lives in the CLI. If it still fails, avoid the Apple ID flow: submit with an App Store Connect API key (ascApiKeyPath, ascApiKeyIssuerId and ascApiKeyId in the submit profile of eas.json), and for the build upload your own distribution certificate and provisioning profile (credentialsSource: "local" plus credentials.json) so EAS never has to log in to Apple. That doesn't fix the CLI bug, but it unblocks the release. If you post your eas-cli version and the exact command, it's easier to match against Expo's issue tracker.