How One Team Rebuilt Their Android CI Pipeline After Six Costly Mistakes
A development team shipping two Android apps from a single Expo React Native codebase hit recurring roadblocks using EAS's free build tier, including exhausted build queues and laptop-frying local builds lasting up to 20 minutes. To resolve this, they migrated their entire Android build and Play Store release process to GitHub Actions, where they had unused free CI minutes. Along the way, they encountered silent versioning failures caused by a gitignored local counter that reset on fresh CI runners, and a Google Play versionCode conflict triggered by a long-forgotten upload on an inactive track. A misleading 'release targeting no countries' error turned out to stem from their pipeline quietly publishing to the wrong Play Store track entirely. The team also discovered that coupling code merges to releases caused unnecessary rebuilds and mid-review resubmissions for apps that had already shipped successfully.
This is an AI-generated summary. ShortSingh links to the original source for the complete article.
Discussion (0)
Log in to join the discussion and vote.
Log in