Automating React Native Deployments

Rate this content

In this talk Cecelia will walk through some options for integrating automation into your React Native deployments, including configuration, testing, code signing, and app store uploads. Whether you are just getting started with automation or want to build a full CI/CD pipeline, this talk will have tactical examples you can start using for your own React Native app.

9 min
15 Nov, 2023

Video Summary and Transcription

This Talk discusses the benefits of automating React Native app deployments and explores tools like Trapeze for automating configuration updates and GitHub Actions for automating the build process. It also highlights the use of signing credentials tooling and cloud credentials management tools like Fastlane Match or AppFlow for more complex builds. The Talk emphasizes the automation of build upload and testing using tools like App Store Developer APIs, Fastlane, Bitrise, or AppFlow, with a specific focus on Fastlane's ability to increment build numbers, build the app, and upload it to TestFlight.

Available in Español

1. Introduction to Automating Deployments

Short description:

Hi, welcome to Automating React Native Deployments. I am Cecilia Martinez, a developer advocate for AppFlow. Today, I'll talk about shipping React Native apps and the benefits of automation in the deployment process. We'll start with automating configuration using tools like Trapeze to update build numbers. Then, we'll explore automating the build process for native iOS and Android.

Hi, welcome to Automating React Native Deployments. I am Cecilia Martinez. I am a developer advocate for AppFlow, the CI CD platform built by Ionic. You can feel free to connect with me on Twitter or GitHub, at Cecilia Creates, or on LinkedIn using my name, Cecilia Martinez.

I'm here today to talk to you about shipping React Native apps, specifically the deployment process. For many developers the deployment process is very manual and very complex. You have to prepare your app code for distribution, you have to compile the signed native binary. You also have to deliver that native binary to the app stores, both for iOS and for Android, and deploy that to manual testers in order to actually make sure that your application works as expected. Once you've gone through all of that, you still have to publish your app for all users and ensure that you have ongoing support.

Now there are some benefits to implementing automation into this process. So in this talk we're going to review some ways that you can incrementally implement automation into certain high impact areas of the deployment process. First we'll start talking about configuration. So, one of the areas where you can implement automation in the configuration aspect is to auto-update configuration values like the Build ID. So typically for each new version of your application, you're going to want a fresh build number for iOS and a version code for Android. This can be very tedious to do manually, especially for React Native apps because you need to go into the source code for each of those platforms and update it. Being able to do this automatically in a CI environment makes it much easier and ensures that all your developers are on the same page.

To do this, you can use a tool like Trapeze. Trapeze is a free and open source tool built by Ionic. You can learn more at But Trapeze allows you to use YAML to create a file that contains instructions for how you'd like to configure native applications. In this case, we are using a CI build number environment variable. This is typically provided by your CI CD environment. Whether you're using GitHub Actions, CircleCI, or in this case, we're talking about AppFlow, you can update this to be whatever the CI build number environment variable is. We're then matching that CI build number to either the iOS build number or your Android version code, depending on what platform that you're building for. Then in your package.json for your React native app, you will have a script. In this case, we have a CI configure script that will run Trapeze and reference that CI.yaml file that we just looked at. Based on what platform that you're building for, again, this is an environment variable provided by your CI CD provider, you will update either that iOS build number or the Android version code. This is not only helpful to ensure that you always have a fresh build number but it's also good for things like debugging, for testing, and grabbing build blogs from your CI environment because it will always match up to the version code of your app.

Next let's talk about building. If you would decide to automate your build process, it can be really high impact because there's so much that goes into building for native iOS and Android.

2. Automating the Build Process

Short description:

To automate the build process for a React Native app, you need to trigger the native build, install the required dependencies, apply signing credentials, and upload the build artifact. A simple example using GitHub Actions for an Android debug build is discussed, including the trigger, dependency installation, bundling the app, and creating the native assemble debug binary using Gradle. For more complex builds, such as Android release or iOS builds, additional steps are required, including specifying keystore information and encoding/decoding files and passwords. It is recommended to use signing credentials tooling or cloud credentials management tools like Fastlane Match or AppFlow.

You need to trigger the native build. You need to install the dependencies that are required for your build. If you're building for release or for App Store you need to decode and apply signing credentials as well as finally upload that build artifact.

Let's take a look at a GitHub Actions example for a simple Android debug build. This is probably the simplest automated build that you can do. The trigger is workflow dispatch. This is a manual dispatch but you could do things like pushing to a branch or a new commit. We're running on Linux and we're checking out our code.

Here's where we're installing our dependencies. Even though Java and Android Studio is installed in GitHub Actions by default, we do need to set it up to be the correct version to correspond to our React Native app. We also want to cache Gradle for improved performance. We're also installing the dependencies that we need for React Native. In this next step here we're bundling the app. This is required before you actually build when you're doing Android debug. Then we're going to use Gradle to actually create that native assemble debug binary. Ultimately we want to ensure that that APK file gets out of our build environment. We're using the upload build artifact GitHub Action. We're also passing through that path in order to be able to access that APK file.

Now, as I mentioned, this is about the simplest one you can do. It's an Android debug build. We don't need any signing credentials. If you're doing an Android release build or any kind of iOS build, not for simulators, then it gets a lot more complicated. For Android, you'll need to specify your keystore file, password, key alias, and key password in your build.gradle file. However, the more complicated part is ensuring that these files and passwords are available in your CI environment. Because it's a file and not just a text-based password, you're going to need to actually encode that in base64 and then decode that in part of your build process. For iOS, for example, this is what it looks like with GitHub Actions. You have in your secrets, you have your store base64 certificate and provisioning profile as well as the passwords, but then you also do need to encode and decode that. Because this can get super complicated and easy to mess up, I highly recommend that you use signing credentials tooling. This can be pre-built steps or actions, so if you're using GitHub Actions or it could be incorporated into like CircleCI for your CI-CD environment, or you can use a tool for cloud credentials management like Fastlane Match or AppFlow. As an example, in AppFlow, you can upload your Android and iOS credentials that are stored on AppFlow servers.

3. Automating Build Upload and Testing

Short description:

Whenever you create a new build, the signing certificate is automatically applied based on the target platform and build type. Uploading and testing can be automated using tools like App Store Developer APIs, Fastlane, Bitrise, or AppFlow. Fastlane, an open source tool maintained by Google, allows you to define steps in a FAST file to increment the build number, build the app, and upload it to TestFlight. If using a mobile CICD platform like AppFlow, you can create an automation that connects to your App Store Connect account and automatically builds and uploads new versions to TestFlight.

Then, whenever you create a new build, you automatically apply the signing certificate that corresponds to the target platform and build type. So we handle all of that decoding and encoding for you, so that you don't have to worry about it as part of your build.

Finally, let's take a look at uploading and testing and how you can incorporate automation here. Now, whenever you want to distribute the binaries that you've just created to your manual testers, you'll typically use Google Play Console or App Store Connect in order to distribute to testing tracks or to test flight. If you want to do this automatically, this upload step, you can leverage App Store Developer APIs. You can also use a CICD integration tool like Fastlane. Or you can also use a mobile CICD platform like Bitrise or AppFlow to automate this upload step.

Let's take a look at Fastlane first. Fastlane is an open source tool currently maintained by Google. You can learn more at With Fastlane, you create a kinda yaml-type file called a FAST file, but it has its own syntax. So, in the first lane, as you can see here, we have a number of steps that we're performing. We're gonna increment the build number, we're gonna build the app, and then we're gonna upload it to TestFlight. These are steps that are provided by Fastlane. However, you do need to ensure that your credentials and everything is set up in your environment so that you can actually connect to your App Store Connect account.

If you're using a mobile CICD platform such as AppFlow, you can create an automation that also connects to your App Store Connect account. So here, we have a TestFlight automation that whenever we push to our Git main branch, it creates a new iOS App Store build using our signing certificate, and then it uploads it to the App Store to our TestFlight destination. This means that every time I push a change, a new version is uploaded to App Store Connect and is immediately available to all of my TestFlight testers.

Well, we covered a lot in a very short time, so if you are looking for more ways to automate your React Native deployments, check out this free ebook, Solving Mobile CICD with AppFlow, using the link of the QR code on the screen. And feel free to reach out to me if you have any questions. Again, I'm at Cecilia Creates.

Check out more articles and videos

We constantly think of articles and videos that might spark Git people interest / skill us up or help building a stellar career

React Advanced Conference 2023React Advanced Conference 2023
29 min
Raising the Bar: Our Journey Making React Native a Preferred Choice
At Microsoft, we're committed to providing our teams with the best tools and technologies to build high-quality mobile applications. React Native has long been a preferred choice for its high performance and great user experience, but getting stakeholders on board can be a challenge. In this talk, we will share our journey of making React Native a preferred choice for stakeholders who prioritize ease of integration and developer experience. We'll discuss the specific strategies we used to achieve our goal and the results we achieved.
React Finland 2021React Finland 2021
27 min
Opensource Documentation—Tales from React and React Native
Documentation is often your community's first point of contact with your project and their daily companion at work. So why is documentation the last thing that gets done, and how can we do it better? This talk shares how important documentation is for React and React Native and how you can invest in or contribute to making your favourite project's docs to build a thriving community
React Day Berlin 2023React Day Berlin 2023
29 min
Bringing React Server Components to React Native
React Server Components are new topic in community, bunch of frameworks are implementing them, people are discussing around this topic. But what if we could use React Server Components in React Native? And bring all optimisation features that RSC allows to mobile apps? In this talk I would present what we are able to do with RSC in React Native!
React Advanced Conference 2021React Advanced Conference 2021
21 min
Building Cross-Platform Component Libraries for Web and Native with React
Top Content
Building products for multiple platforms such as web and mobile often requires separate code-based despite most of the components being identical in look and feel. Is there a way where we could use shared React component library on different platforms and save time? In this presentation I'll demonstrate one way to build truly cross-platform component library with a unique approach of using React & React Native in combination.

Workshops on related topic

React Advanced Conference 2022React Advanced Conference 2022
81 min
Introducing FlashList: Let's build a performant React Native list all together
Top Content
In this workshop you’ll learn why we created FlashList at Shopify and how you can use it in your code today. We will show you how to take a list that is not performant in FlatList and make it performant using FlashList with minimum effort. We will use tools like Flipper, our own benchmarking code, and teach you how the FlashList API can cover more complex use cases and still keep a top-notch performance.You will know:- Quick presentation about what FlashList, why we built, etc.- Migrating from FlatList to FlashList- Teaching how to write a performant list- Utilizing the tools provided by FlashList library (mainly the useBenchmark hook)- Using the Flipper plugins (flame graph, our lists profiler, UI & JS FPS profiler, etc.)- Optimizing performance of FlashList by using more advanced props like `getType`- 5-6 sample tasks where we’ll uncover and fix issues together- Q&A with Shopify team
React Summit 2022React Summit 2022
117 min
Detox 101: How to write stable end-to-end tests for your React Native application
Top Content
Compared to unit testing, end-to-end testing aims to interact with your application just like a real user. And as we all know it can be pretty challenging. Especially when we talk about Mobile applications.
Tests rely on many conditions and are considered to be slow and flaky. On the other hand - end-to-end tests can give the greatest confidence that your app is working. And if done right - can become an amazing tool for boosting developer velocity.
Detox is a gray-box end-to-end testing framework for mobile apps. Developed by Wix to solve the problem of slowness and flakiness and used by React Native itself as its E2E testing tool.
Join me on this workshop to learn how to make your mobile end-to-end tests with Detox rock.
Prerequisites- iOS/Android: MacOS Catalina or newer- Android only: Linux- Install before the workshop
React Summit Remote Edition 2021React Summit Remote Edition 2021
60 min
How to Build an Interactive “Wheel of Fortune” Animation with React Native
Top Content
- Intro - Cleo & our mission- What we want to build, how it fits into our product & purpose, run through designs- Getting started with environment set up & “hello world”- Intro to React Native Animation- Step 1: Spinning the wheel on a button press- Step 2: Dragging the wheel to give it velocity- Step 3: Adding friction to the wheel to slow it down- Step 4 (stretch): Adding haptics for an immersive feel
React Advanced Conference 2023React Advanced Conference 2023
159 min
Effective Detox Testing
So you’ve gotten Detox set up to test your React Native application. Good work! But you aren’t done yet: there are still a lot of questions you need to answer. How many tests do you write? When and where do you run them? How do you ensure there is test data available? What do you do about parts of your app that use mobile APIs that are difficult to automate? You could sink a lot of effort into these things—is the payoff worth it?
In this three-hour workshop we’ll address these questions by discussing how to integrate Detox into your development workflow. You’ll walk away with the skills and information you need to make Detox testing a natural and productive part of day-to-day development.
Table of contents:
- Deciding what to test with Detox vs React Native Testing Library vs manual testing- Setting up a fake API layer for testing- Getting Detox running on CI on GitHub Actions for free- Deciding how much of your app to test with Detox: a sliding scale- Fitting Detox into you local development workflow
- Familiarity with building applications with React Native- Basic experience with Detox- Machine setup: a working React Native CLI development environment including either Xcode or Android Studio
React Summit 2023React Summit 2023
88 min
Deploying React Native Apps in the Cloud
Deploying React Native apps manually on a local machine can be complex. The differences between Android and iOS require developers to use specific tools and processes for each platform, including hardware requirements for iOS. Manual deployments also make it difficult to manage signing credentials, environment configurations, track releases, and to collaborate as a team.
Appflow is the cloud mobile DevOps platform built by Ionic. Using a service like Appflow to build React Native apps not only provides access to powerful computing resources, it can simplify the deployment process by providing a centralized environment for managing and distributing your app to multiple platforms. This can save time and resources, enable collaboration, as well as improve the overall reliability and scalability of an app.
In this workshop, you’ll deploy a React Native application for delivery to Android and iOS test devices using Appflow. You’ll also learn the steps for publishing to Google Play and Apple App Stores. No previous experience with deploying native applications is required, and you’ll come away with a deeper understanding of the mobile deployment process and best practices for how to use a cloud mobile DevOps platform to ship quickly at scale.
React Advanced Conference 2022React Advanced Conference 2022
131 min
Introduction to React Native Testing Library
Are you satisfied with your test suites? If you said no, you’re not alone—most developers aren’t. And testing in React Native is harder than on most platforms. How can you write JavaScript tests when the JS and native code are so intertwined? And what in the world are you supposed to do about that persistent act() warning? Faced with these challenges, some teams are never able to make any progress testing their React Native app, and others end up with tests that don’t seem to help and only take extra time to maintain.
But it doesn’t have to be this way. React Native Testing Library (RNTL) is a great library for component testing, and with the right mental model you can use it to implement tests that are low-cost and high-value. In this three-hour workshop you’ll learn the tools, techniques, and principles you need to implement tests that will help you ship your React Native app with confidence. You’ll walk away with a clear vision for the goal of your component tests and with techniques that will help you address any obstacle that gets in the way of that will know:- The different kinds React Native tests, and where component tests fit in- A mental model for thinking about the inputs and outputs of the components you test- Options for selecting text, image, and native code elements to verify and interact with them- The value of mocks and why they shouldn’t be avoided- The challenges with asynchrony in RNTL tests and how to handle them- Options for handling native functions and components in your JavaScript tests
Prerequisites:- Familiarity with building applications with React Native- Basic experience writing automated tests with Jest or another unit testing framework- You do not need any experience with React Native Testing Library- Machine setup: Node 16.x or 18.x, Yarn, be able to successfully create and run a new Expo app following the instructions on