After reading all docs about EAS build, EAS update, EAS auto submission AND Deployment pattern I’m a bit lost and don’t understand what I need to do to make it work…
I have several questions:
How to differentiate production and staging builds?
Both have the same version (eg 1.0.0) but they only have
If it’s auto-incrementing, how can I tell which is which.
Automating submissions suggest to use different
But EAS update only uses one bundleIdentifier/package with specific channel name.
What should we do if we want to build with a specific configuration AND channel ?
packageand two channels ?
packageand one channel ?
If Triggering builds from CI how to differentiate if an EAS build is needed or only EAS update (small changes) ?
If building needs to have there
versionCodeincremented for each new build.
How should we do with Triggering builds from CI on staging branch AND production branch ?
With eas.json build.xxxxx.[android/ios].autoIncrement at
true, the build will trigger increment of the
versionCode(which is good).
But if we commit on production that triggers a CI:
- CI will build
- Changing the build number
- eas.json file need to be committed (because it changes) to keep track of the last version built.
Should we need to commit changes inside production branch AND staging branch ?
But what if the staging is headed of production? (eg: staging => 41 and production => 38)