Expo EAS Config Generator

EAS Build (Expo Application Services) is Expo's cloud build service that replaced the classic 'expo build' command. Key differences: EAS supports bare workflow (ejected apps) and managed workflow, produces native binaries (.ipa for iOS, .apk/.aab for Android), supports custom native code, and offers configurable build environments. Classic expo build is deprecated; EAS is now the recommended approach for all Expo projects.

Development profile: includes dev client (Expo Dev Client), enables debugging, connects to your local dev server. Use for active development. Preview profile: internal distribution build (ad-hoc for iOS, APK for Android), no dev client, used for testing with stakeholders before store submission. Production profile: optimized build for app stores, code signing for release, App Store / Google Play ready. Each profile can have different environment variables, credentials, and build configuration.

Yes, eas.json should be committed to your repository. It contains build configuration but not secrets. Sensitive values like API keys should be stored as EAS Secrets (set via 'eas secret:create') and referenced as environment variables in eas.json. The eas.json file defines your build profiles, channel assignments, and distribution settings — all of which should be versioned alongside your code.

Managed workflow: Expo handles all native code. You don't have android/ or ios/ directories. Configuration is done via app.json/app.config.js. Best for simpler apps without heavy native customization. Bare workflow: You have full access to native code (android/ and ios/ directories exist after 'expo eject'). You can add any native module. Requires more native build knowledge. EAS Build supports both, but eas.json configuration differs slightly — bare workflow often needs prebuild steps.

EAS handles certificate management automatically. Run 'eas credentials' to set up. For development: EAS creates a development certificate and provisioning profile automatically. For App Store distribution: EAS can create and manage your distribution certificate and provisioning profile using your Apple Developer account credentials. You can also use existing certificates by running 'eas credentials --platform ios'. EAS stores credentials securely in their servers, avoiding the need to manage .p12 files manually.