this is because we use CI on biterise, not build locally.
I know build locally is not a issue as expo cli will store the cookie locally. it will only ask the verify code at the first time.
but for bitrise, it is not working as every time it is a new machine.
do expo have any solution to skip the 2fa steps of apple? like APP-KEY?
Hi, @adamjnav, we’re observing this issue as well where we run “eas build --platform ios” and getting the following error:
“Authentication with Apple Developer Portal failed!
Error: Need to acknowledge to Apple’s Apple ID and Privacy statement. Please manually log into https://appleid.apple.com (or https://appstoreconnect.apple.com) to acknowledge the statement.”
We logged into both websites, and no agreements or anything popped up.
Apparently Apple now demands you authenticate with them using API Keys. This is what have found out, after days of no being able to build with the cli.
In an effort to keep your account more secure, two-factor authentication is required for Account Holders of a developer program to sign in to their Apple Developer account and Certificates, Identifiers & Profiles. Starting February 2021, two-factor authentication or two-step verification will be required for all users to sign in to App Store Connect. This extra layer of security for your Apple ID helps ensure that you’re the only person who can access your account.
1: use skip-credentials-check when run expo build:ios
2: 2FA now is madantory, but expo cli does not support APPLE API key
3: solution is use bitrise to upload, it have a solution to use apple password with apple APP specified key.
“solution is use bitrise to upload” - what do you mean? eas submit uses an app specific password to upload to the app store and that works fine. we no longer support expo upload:ios (which uses fastlane under the hood) but it also supported using app specific password.
expo-cli supports 2fa with apple. you should enable that.
eas submit works great, i am not aware of any instability issues, but it is in feature preview still. eas build is a bit earlier and more complicated, in particular around managed workflow app support - we’ll launch preview support there at end of q1 most likely.
We’ve been doing a standalone build with an Enterprise Developer account for quite a while but now, as others have mentioned, that build is failing.
After reading through this thread I even tried to run the build with the “–skip-credentials-check” flag… it appeared to work but after about 10 mins or so it failed with “ Build failed. Standalone build failed!”
(Note: I do not need to upload the app to the App store. I’m using expo to build the app with an Enterprise account and then distribute the app from my client’s servers.)
Thanks @notbrent that ended up solving the first issue.
As a follow up issue:
My client invited me to join their Apple Developer org and gave me the “Developer” role… it appears like that role doesn’t have sufficient privileges as I’m now getting the following error when running the tool with my account: "This request is forbidden for security reasons - You are not allowed to perform this operation. Please check with one of your Team Admins, or, if you need further assistance, please contact Apple Developer Program Support"
Anyone know what privilege level my Apple Developer account needs to have in order to run the iOS builds?
Build failed. Standalone build failed!”