Web Developers : 7-Update Version and Build Numbers for iOS and Android Apps Using EAS

Screenshot from the tutorial

Updating Version and Build Numbers for iOS and Android Apps Using EAS

In the fast-paced world of mobile app development, keeping your application up-to-date is crucial. One important aspect of this process is managing the version and build numbers for your iOS and Android apps. In this blog post, we will walk through how to update these numbers using Expo Application Services (EAS) in just a few minutes.

Understanding Version and Build Numbers

Before diving into the technical details, it’s essential to understand the difference between version and build numbers:

• Version Number: This is the user-facing number that indicates the release version of the app. It usually follows the format X.Y.Z (Major.Minor.Patch). For example, 1.0.0.

• Build Number: This is an internal number that helps developers track the specific build of the app. It is typically incremented with every new release and can be a simple integer or a more complex string.

Why Update Version and Build Numbers?

Updating version and build numbers is essential for several reasons:

1. User Recognition: Helps users identify new releases.
2. App Store Compliance: Both Apple and Google require versioning for app submissions.
3. Debugging: Easier tracking of issues and improvements across different builds.

Prerequisites

To follow this tutorial, ensure you have:

• An Expo project set up with EAS configured.

• The EAS CLI installed. If you haven’t installed it yet, run:

  npm install -g eas-cli
  

Step-by-Step Guide to Update Version and Build Numbers

Step 1: Navigate to Your Project Directory

Open your terminal and navigate to the root directory of your Expo project:

cd /path/to/your/expo/project

Step 2: Update app.json or app.config.js

EAS reads your version and build numbers from the app.json or app.config.js file. Open this file in your preferred code editor.

In your app.json, locate the version and buildNumber (iOS) and versionCode (Android) properties. For example:

{
  "expo": {
    "name": "YourAppName",
    "slug": "your-app-slug",
    "version": "1.0.0",
    "ios": {
      "buildNumber": "1.0.0"
    },
    "android": {
      "versionCode": 1
    }
  }
}

Step 3: Increment Version and Build Numbers

Update the version, buildNumber, and versionCode:

• Version: Increment the version according to semantic versioning (e.g., from 1.0.0 to 1.0.1).
• Build Number: Increment the build number (e.g., from 1.0.0 to 1.0.1).
• Version Code: This should be an integer that increments with each build (e.g., from 1 to 2).

Updated example:

{
  "expo": {
    "name": "YourAppName",
    "slug": "your-app-slug",
    "version": "1.0.1",
    "ios": {
      "buildNumber": "1.0.1"
    },
    "android": {
      "versionCode": 2
    }
  }
}

Step 4: Save Changes

After making the necessary updates, save the changes to your app.json or app.config.js file.

Step 5: Build Your App

Now that your version and build numbers are updated, you can build your app using EAS. Run the following command:

eas build --platform all

This command will create builds for both iOS and Android platforms.

Step 6: Verify Your Changes

After the build process is complete, check the generated apps to ensure that the new version and build numbers appear correctly. You can do this by installing the app on your device or using the App Store or Play Store listing.

Conclusion

Updating version and build numbers is a straightforward process that can significantly impact your app’s visibility and compliance in app stores. By following the steps outlined above, you can quickly ensure that your mobile application is up-to-date and ready for users.

Remember to always test your app after making these updates to ensure everything functions as expected. Happy coding!

Another view from the tutorial

---

Connect with SkillBakery Studios

Explore more tutorials, tools, and resources:

• skillbakery.com
• Facebook
• X (Twitter)
• YouTube Channel

Posted by SkillBakery Studios