I noticed that when setting up CI,
eas build -p ios will skip Provisioning Profile validation. I see we can pass environment variables so that
eas build can authorise with apple connect, as documented here: Triggering builds from CI - Expo Documentation
My question is, since
eas submit has the functionality to manage credentials, could
eas build simply use those hosted credentials on expo servers for its needs too? Specifically, expo created and is now hosting all information for a ASC Api key when the first submission was done. I can login to my expo dashboard and view all the information the previous document was requesting I store in environment variables.