Deploying React Native Expo Apps Without EAS (Free Tier) and Managing Build Delays

[gotoenchanter]

When using Expo, the EAS Build service (especially the free tier) can cause delays in building and deploying apps due to queue times.

If a developer wants to work and deploy without relying on EAS, what options exist for local or alternative builds?

Specifically:

• How can we build and deploy Expo apps locally for iOS and Android without EAS?
• What are the limitations and requirements for bypassing EAS builds, particularly for iOS app signing?
• Are there workflow best practices for managing development, testing, and production builds without a premium EAS subscription?

[codingwizard0831]

Expo provides several ways to build and deploy apps without relying on EAS, although some features (like iOS automatic signing) are limited on the free tier.

---

1. Using Classic Expo Build (expo build)

Note: expo build is deprecated in favor of EAS, but it still works for many workflows.

expo build:android
expo build:ios

• Generates a standalone APK (Android) or IPA (iOS).

• Limitations:

  • iOS: Requires an Apple Developer account; you must manually manage certificates and provisioning profiles.
  • Build times may still be queued if using Expo servers, but Android builds are generally faster.

---

2. Local Builds with expo-cli + react-native

For full local control, you can eject to the bare workflow and use native build tools:

expo eject

• Converts your project to a bare React Native project, giving access to Xcode and Android Studio.
• You can now build locally:

Android (local build APK):

cd android
./gradlew assembleRelease

• Generates a release APK in android/app/build/outputs/apk/release/app-release.apk.

iOS (local build IPA):

cd ios
xcodebuild -workspace YourApp.xcworkspace -scheme YourApp -configuration Release -sdk iphoneos

• Requires Xcode and proper provisioning profiles/certificates.

Advantages:

• No EAS queue delays.
• Full control over build environment.
• Supports custom native modules and advanced configuration.

Limitations:

• Manual signing for iOS.
• Need to maintain local Android/iOS build environments.

---

3. Development & Testing Without EAS

For daily development, you don’t need EAS:

• Use Expo Go to test on devices or simulators.

  expo start

• Use React Native CLI for testing features that require custom native modules.

---

4. Workflow Recommendations Without EAS

1. For Android: Use local Gradle builds for production APK.

2. For iOS: Either:

   • Use local Xcode builds (requires Apple Developer account), or
   • Use Expo’s classic expo build:ios (manual certificates).

3. Testing & QA: Use Expo Go or internal test builds with Firebase App Distribution or TestFlight.

4. CI/CD: Consider GitHub Actions or Fastlane to automate local builds and deployment.

---

Example: Local Android Build Workflow

expo eject
cd android
./gradlew assembleRelease
# APK output: android/app/build/outputs/apk/release/app-release.apk
adb install android/app/build/outputs/apk/release/app-release.apk

• Installs the release APK directly on a connected Android device.
• No EAS queue required.

---

Summary:

• EAS is convenient but may delay builds on the free tier.
• For full control, eject to bare workflow and build locally using Gradle (Android) or Xcode (iOS).
• Manual management of certificates and signing is required for iOS.
• Combine with Expo Go and CI/CD automation for smooth development and deployment without EAS.