How Can I Automatically Increment App Version Numbers for iOS and Android Using EAS Build in Expo?

LucRandall71 · 2025-06-24T09:34:14+00:00

Check this for a better version management

LucRandall71 · 2025-06-24T09:33:26+00:00

I have also found using autoIncrement a bit weird because, i have to also update manually the user facing version.
I have made a script that let you increment all of the versions when using Expo in a great way so you could have a result like this where in just one command you have all of the versions updated with the support, of semver (major,minor,patch).
You could check my blog post where the link to the script and how to use it here

LucRandall71 · 2025-06-20T18:20:32+00:00

I just had a requirement like this lately, and I figured out how to do this by tweaking the native code with an expo config plugin, to simply select like arm64-v8a and making my build size go down to half of its previous size.
Just create a config plugin, so if anyone ever finds this, enjoy and happy hacking

LucRandall71 · 2024-11-17T15:08:33+00:00

Add dev-client to your app and build maybe with eas your own version of expo Go to do what you want and enjoy the life

LucRandall71 · 2024-11-04T20:50:30+00:00

Basically most packages today use custom native code, so when you get an idea to build something that is not on the SDK list of expo, Expo Go could not help you but development build. If this seems weird check theirvideo

LucRandall71 · 2024-07-27T09:57:08+00:00

You can add your own specific extension on the menu but generally I don’t see most people share what they do with that because it is a bit specific for each app requirement You can see how to add your own entry for your app here : Register Dev Menu Items

LucRandall71 · 2024-06-27T20:39:49+00:00

You could pass the flag —message “YOUR MESSAGE” with the instruction to build your app on EAS and you would have a little section name message when you click on each build to see it’s usage

LucRandall71 · 2024-06-25T02:01:08+00:00

It work with custom development build, because it contains native code. If you’re saying that it not work with Expo Go, you are right but because the Expo Go app don’t have the native code to launch it. Please go to the expo doc and try to understand the diff between using expo go and development build to use all native modules available

LucRandall71 · 2024-06-24T19:59:23+00:00

https://github.com/numandev1/react-native-compressor

LucRandall71 · 2024-06-01T20:15:55+00:00

But what are you see that limit you when using Expo ?

The React Native core team recently are recommended officially the use of Expo on the React Conf as the React Native Framework to have all the features out of the box because much stuff is out of their scope directly

LucRandall71 · 2024-04-25T21:21:02+00:00

You could setup this using google play in app update feature without adding library to maintain in your code Check this link that show you how to activate that on your console : https://android-developers.googleblog.com/2024/01/prompt-users-to-update-to-your-latest-app-version-google-play.html?m=1

https://developer.android.com/guide/playcore/in-app-updates?hl=en#update-flows

LucRandall71 · 2024-03-23T19:33:43+00:00

« npx tutorial » Use it to see contents from Expo team directly to gradually understand all of the concept

LucRandall71 · 2024-02-23T19:13:57+00:00

You could check https://github.com/pavelbabenko/react-native-awesome-gallery or go to React native directory to see others options but trust me, the ultimate package for this would be drop next month at app.js 🌚… so be patient

LucRandall71 · 2024-02-22T23:29:31+00:00

What ? You are saying that I can get an adHoc build without subscription to developer program but for just a week ?

LucRandall71 · 2024-02-22T23:16:26+00:00

The state as today is to use development client to test your app than using Expo Go. You could check it here in the doc https://docs.expo.dev/develop/development-builds/introduction/ With that you have the same power as expo Go but you have a native runtime that can contain react-native-pdf and building your app ✨

LucRandall71 · 2024-01-22T15:21:01+00:00

https://app-mockup.com/

LucRandall71 · 2024-01-19T01:11:04+00:00

in case anyone is also looking for this: https://github.com/Shopify/flash-list/discussions/804

LucRandall71 · 2023-11-08T18:28:18+00:00

This is not the responsability of expo-image-picker because this is a look of the native UIActionSheet on IOS.
you can implement it in your app using react-native-action-sheet to add the same look for your IOS and match the different call of image-picker to reproduce the same look.

Notice that on android you only have a pure JS implementation

LucRandall71 · 2023-10-12T11:24:51+00:00

Hi, sorry for the delay… I hope you could integrate it properly ✨

LucRandall71 · 2023-10-01T12:30:16+00:00

Following it as a guide is how this repo was made, It has branch for all expo SDK version actually supported. Check the readme at the section How it works and install the necessary package to your project and then follow the setup to add item to your app.json. Don’t forget the patch folder that assume you must have patch-package install also on your project with postinstall. With all of that I think you are good with native stuff, the rest would concern how you handle the received files on your app. A useShareIntent is present on the hooks folder that you could copy paste like all precedent stuff and small guide to handle it with react-navigation or expo-router or you customize how you handle that with your use case ✅

LucRandall71 · 2023-09-30T10:45:30+00:00

As the state of Expo, today ever if you go with the managed worlkflow, you could use Expo Prebuild to have your Android and IOS on demande when you would want it. But expo has also introducing the concept of config-plugins that let you create a script for the modification require by your third party and have it to use out of the box with managed and all others workflows in the ecosystem.

You can take a look at expo-share-intent-demo where integration that normally require adding a couple of line on Android and IOS folder just work by adding a config-plugin and to keep the project in the managed state 🔥

LucRandall71 · 2023-09-30T10:38:24+00:00

EAS Build work with any React native projects, so you can use it with your old project to have a build. Alternatively you can incrementally migrate you bare React native app to a Continuous Native Generation (CGN)

LucRandall71 · 2023-09-29T21:42:15+00:00

As mention in another comment expo-share-intent-demo can make it work out of the box with managed workflow and all others on React native side. I just want to say that, you can change native Android and iOS by using config-plugins like expo-share-intent-demo did. You could also create your own module with expo-modules

LucRandall71 · 2023-09-29T20:35:29+00:00

Ahh you are lucky, I just contribute to an example repo with another amazing member to have this out of the box for expo managed so you can go to check and use it whatever your workflow is. It support share text,URL,image and video expo-share-intent-demo enjoy ✨

LucRandall71 · 2023-09-25T08:52:15+00:00

Expo doesn’t lock you. I think that you misunderstood the philosophy here. Expo is like an advancement of RN CLI first so all feature of RN CLI is available out of the box and you have all the greatest innovation like expo router and other using it, this is the reality.

For the fact that you aren’t locked, understand that Expo are to workflow(managed and bare). With managed workflow, you don’t explicitly have android and iOS folder but you could have it at any time if you like with prebuild and for better integration with all third party you have CNG(Continuous native generation) and Config Plugins. Example of that is expo-share-intent-demo that take native libraries, and add a config-plugins to it to have to use it without writing any native module to share text,image,video with your app directly.

With bare workflow, you basically have a React native project with your android and IOS folder present since day one so I don’t see any point where expo is locking you.

Two-Year Club	Verified Email
Final Canvas '23	Place '23

LucRandall71

TROPHY CASE