Expo Feature Focus: Expo EAS Build | Automatic App Version Management

0:00 - How and why to utilize automatic app version management
1:05 - Use a remote version source
3:37 - Starting from a different version number
4:15 - Use a local version source
4:46 - Conclusion

#expo #reactnative #ExpoTutorial

[joeycopperson]

Thank you for vid tutorial. It'd be nice if you guys can post more build, release management, testing, analytics, type of tutorials.

[Norfeldt]

Very handy. But what about OTA? I used to use the semver (1.0.0 then 1.1.0 for new native packages) but can expo handle this as well? (Would be nice if it added the git tag for each semver deployed to the app store)

[JB.Creative]

This was priceless! thanks, I was banging my head on my screen trying to figure out why my app would not upload after an update, this fixed my problem and probably saved my sanity

[alexmachin]

How does this work with development builds ? You removed the versionCode for Android, but that's needed right ? Little confused about how this all works exactly.

[ryanaiden]

Anyone who wants auto version names, you can use some clever Unix in GH actions to make sure you can bump up the semantic versioning according to your a prefix you attach to any new branches you create corresponding to the npm version command. I recommend (bug/ | patch/ | boost/ | hotfix/) for npm version patch, (feature/) for npm version minor, and (epic/) for npm version major. I usually do this on a successfully close PR.

[amandps]

That's awesome! I'd love to see more such videos.

[chinfanster]

thanks! That really helps a lot! Keep posting new videos.

[anazi]

THATS AMAZING! One more step and we get the 1.2.3 version style. If this can be incremented OH MY !

Maybe in the future it will automatically detects wither you added new packages or you did a breaking update and based on that it decided to increment the first number 1.0.0 or the second 1.1.0 or if its small tweaks then its 1.0.1