CI/CD: EAS, Fastlane and Store Submission

A web app team can push a change and watch it live within minutes. A React Native team pushing a native change cannot: a compiled binary has to be built, signed with real cryptographic credentials, uploaded to a platform that is not the team's own infrastructure, and reviewed by a process the team does not control and cannot fully predict the timing of. Every one of those steps is a place a manual, ad hoc release process breaks — a certificate that expired without anyone noticing, a build number that was not incremented and gets silently rejected, credentials that live only on one departing engineer's laptop.

CI/CD for mobile is not the same discipline as CI/CD for a backend service wearing a mobile-shaped hat. Signing credentials are long-lived, sensitive secrets that have to be shared safely across a team and across CI runners without ever being committed to source control. Build numbers and version strings have platform-specific monotonicity rules that a script has to enforce, not just suggest. And the final step of the pipeline — submission — hands control to a third party's review process that can reject a build for a policy reason no amount of correct code prevents.

Analogy🏏Cricket

🏏 Think of it like cricket: A touring team's kit and equipment do not simply get thrown in a bag by whoever is free that morning — a dedicated logistics manager owns the checklist for what has to be packed, checked, and cleared through customs for every single leg of an international tour, because a missing piece of certified equipment discovered at the airport, with no time to fix it, can derail preparation for an entire match. Indian cricket's support staff on overseas tours run exactly this kind of dedicated, repeatable logistics process precisely because leaving it to whoever happens to be around that day, without a defined owner and a defined checklist, is how something critical gets missed at the worst possible moment. Just as a dedicated logistics process catches a missing piece of equipment before it becomes a crisis at the airport, a CI/CD pipeline catches a missing credential or an unincremented build number before it becomes a crisis at submission. Just as an ad hoc, whoever-is-free packing process eventually misses something critical, an ad hoc, whoever-is-free release process eventually ships a build that fails signing or gets rejected. The insight is that a process repeated often enough, under enough time pressure, needs to be a defined, owned system — not a habit any one person happens to remember to follow.