How One Dev Team Replaced EAS with GitHub Actions for Android Play Store Releases
A development team at Cyfamod, which ships two Android apps from a single Expo React Native codebase, documented their migration away from EAS's free build tier to a self-hosted GitHub Actions pipeline. The free tier's build queue kept stalling mid-sprint, while local builds monopolised developer laptops for up to 20 minutes at a time, making both options unsustainable. During the migration, a gitignored local version counter failed to persist on fresh CI runners, causing the pipeline to silently ship an incorrect, outdated version number. The team also discovered that Google Play enforces a single, strictly increasing versionCode across all tracks per app, meaning an old forgotten upload on any track can block all future releases. Additionally, Play Console's human-readable release labels do not reflect the actual enforced versionCode, a discrepancy that caused further confusion during the setup process.
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