EAS Feature Branch Builds

Creating Test Builds for Feature Branches (EAS Build)

We use Expo Application Services (EAS) Build to create internal builds (.ipa for iOS, .apk for Android) directly from feature branches for testing purposes before merging to main.

Prerequisites

1. EAS Account & Login: Ensure you have an Expo account and are logged in via the EAS CLI (eas login).
2. EAS Project Setup: The project should be configured for EAS Build (eas build:configure). This is typically done once per project.
3. Internal Distribution Setup:
   • iOS: An Ad Hoc provisioning profile must be configured in eas.json, including the UDIDs of all test devices. See Finding Device UDIDs.
   • Android: Builds can typically be distributed via internal sharing links or potentially Firebase App Distribution (if configured).

Workflow

1. Checkout Feature Branch: Make sure you are on the local feature branch you want to build (git checkout your-feature-branch).
2. Ensure Branch is Pushed: Push your latest commits to the remote repository (git push origin your-feature-branch). EAS Build often works best when building from a remote commit hash.
3. Run EAS Build: Execute the build command, specifying the platform and the desired distribution profile (usually named internal or similar in eas.json).
   • iOS:

     eas build --platform ios --profile internal
     

   • Android:

     eas build --platform android --profile internal
     

4. Monitor Build: EAS CLI will provide a link to monitor the build progress on the Expo website.
5. Distribute Build: Once the build is complete:
   • iOS: The .ipa file can be downloaded from the build details page. It needs to be distributed manually (e.g., via Slack, email, or a simple hosting service) to testers whose device UDIDs are included in the provisioning profile. They can typically install it via Finder or Apple Configurator.
   • Android: The .apk file can be downloaded. It can be shared directly with testers, who will need to enable installation from unknown sources on their devices. Alternatively, if Firebase App Distribution is set up, you can upload the APK there.
6. Provide Build Link/File: Share the downloadable build link (from the EAS build page) or the artifact file itself with the designated testers.

Important Notes

• Build Profiles (eas.json): The internal profile in eas.json defines crucial settings like distribution type (internal/ad-hoc), credentials, and environment variables. Ensure it’s correctly configured.
• Credentials: EAS manages iOS and Android signing credentials. Ensure they are set up correctly for internal distribution (eas credentials).
• Costs: EAS Build operates on a usage-based pricing model. Be mindful of the number and frequency of builds.