-
Notifications
You must be signed in to change notification settings - Fork 75
-
Notifications
You must be signed in to change notification settings - Fork 75
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
running expo build for iOS #65
Comments
Hi @zivl! That should be possible by using environment variables! Based on the envvars used here and the options from the command itself, it should look something like:
You can play around with the options you provide to Can you try this out? I'll add it to the readme if that works as expected 😄 |
@byCedric thanks for the detailed example, yet, Apple uses TFA so I'm afraid |
Ah, you are right! I think that would make any "first time builds" close to impossible, since these TFA codes changes. You'd have to build at least 1 time locally, so you can authenticate with Apple and setup the certificates in advance. After that, you should be able to run the Does that help your use case in any way? |
@byCedric It did work! |
@byCedric I think this issue can be closed, unless you wanna keep it open to grab some documentation out of it |
assuming the flow in which expo is taking care of the entire signature and provisioning stuff for you
do you have an example of how to create an
expo build:ios -t archive
flow, which having the Apple Connect user/pass?The text was updated successfully, but these errors were encountered: