EAS Build and Submit

An Expo app builds every variant on EAS from one checked eas.json, and a store build reaches TestFlight and Google Play internal testing only after the gates passed, from the reviewed commit, with a build number no store has seen and a fingerprint that matches the reviewed native inputs. Credentials stay with EAS and the developer; the agent builds, proves and submits with the developer's word.

Rules that must hold