You've built a React Native app and now it's time to get it in the hands of your users. If you're used to web, dealing with mobile-specific deployment issues can be a struggle. There are native build hardware and config requirements, signing certificates, app store approvals, app versions, pushing updates, and more. You also have to consider all the tooling options -- do you manually deploy on your own, use a React Native-specific solution, or try to configure web CI/CD for mobile? This crash course will outline the build and ship process and review some common tools in the React Native ecosystem so you can feel confident deploying and get back to developing.
Code Signing React Native Apps
Video Summary and Transcription
Code signing is a critical step in preparing React Native apps for mobile devices. Generating a signed bundle requires different credentials for Android and iOS. Automating signed builds using a cloud CI-CD provider like AppFlow simplifies the process. AppFlow handles native iOS and Android builds in the cloud, including managing signing credentials. It allows for on-demand builds, automated workflows, and deployment to app stores.
1. Code Signing React Native Apps
Code signing is a critical step in preparing your React Native apps to run on mobile devices. To generate a signed bundle of your React Native app for Android, you'll need to generate an upload Keystore. For iOS apps, you need two credentials, a signing certificate, and a provisioning profile.
Hello, I'm Cecilia Martinez, Developer Advocate for AppFlow, the mobile CI CD platform built by Ionic. This is Code Signing React Native Apps. Code signing is a critical step in preparing your React Native apps to run on mobile devices. This process signs your app with secure credentials during the build process. It's required by both iOS and Android apps, but the process is different for each platform. If you plan to automate your mobile builds in CI CD, you'll need to make sure that your credentials are in your cloud environment, so understanding how they work is critical for a seamless app delivery process.
Let's start with Android. To generate a signed bundle of your React Native app for Android, you'll need to generate an upload Keystore. During the process of generating it, you want to make sure that you take note of the Keystore path, alias, Keystore password and key password. An upload Keystore can be generated in Android Studio or by using Keytool, which is a CLI tool that comes built into the Android Studio SDK. Make sure not to lose the file, as it lives on for the life of the application, although if you do lose it, you can update it if needed, but only if you're using Google Play App Signing. To generate an Android Studio, click the Generate Signed Bundle, or APK, and then follow the instructions to generate a key. Make sure to take note of the path where the Keystore is saved and the alias and passwords. For Keytool, you're going to run the Keytool command with the genKey flag and then pass the keystore file name, alias, algorithm, size, the length of the time before it expires, and the store type. The CLI will prompt you for your information and then create the Keystore in the same directory that you run the command. You can complete the process of generating a sign bundle in Android Studio, but if you want to build via the command line or in CICD, you're going to need to add your Keystore info to the signing config block within your app.build.gradle file in your React Native project. This lets Gradle know where to find your signing credentials when it's time to build.
Things get a little more complicated with Apple. For iOS apps, you need two credentials, a signing certificate, and a provisioning profile. You do need an Apple Developer Program account in order to generate these. And if you plan to use Xcode for generation, make sure that you connect that Apple Developer Program account to Xcode. Signing certificates validate the identity of who generated the build and that they're authorized to do so. This is a P12 file. To generate an Xcode, you can do this by going to Settings, then Accounts, and then Manage Certificates. Click the plus icon and select the certificate type. You can then right click and export the P12 certificate, making sure that you give it a strong password. To generate a signed certificate from the Apple Developer Program, you're first going to need to generate a signed certificate request file. This is done using Certificate Assistant and Keychain Access. Then upload that request file to the Apple Developer Program to create a certificate. This will generate a .cer file, which then you can use Keychain Access or OpenSSL to convert to a P12.
2. Signing and Automating Builds with AppFlow
To generate a signed bundle of your React Native app, you'll need to generate an upload Keystore for Android and a signing certificate and provisioning profile for iOS. If you're doing a development or ad hoc build, you will have to register your devices in the Apple Developer Program to create the Provisioning Profile. Automating signed builds using a cloud CI-CD provider can be tricky, but AppFlow makes it easier. AppFlow is the mobile CI-CD platform built by Ionic that handles your native iOS and Android builds in the cloud, including the management of signing credentials. You can upload your credentials to the AppFlow dashboard and use them for on-demand builds or automated workflows. AppFlow takes care of altering your React Native Gradle config and allows you to select the signing credentials and build specifications for each build. You can also create automated workflows and deploy to the Apple App Store or Google Play Store.
For Keychain Access, you'll go ahead and double-click that .cer file and export it as a P12. Now that you have your signed certificate, the next is the Provisioning Profile. A Provisioning Profile states what devices a signed bundle can run on. If you're doing a development or ad hoc build, you will have to register your devices in Apple Developer Program in order to create the Provisioning Profile.
You can register devices in ADP, or you can connect them to Xcode manually in order to register. If you're building locally in Xcode and using automatic signing, Xcode will build the mobile provisioning profile for you based on the build type that you select. To create a new provisioning profile in the Apple Developer Program, you'll select the profile type, the app, and then your signed certificate and any devices. You'll finally give it a name and generate. Then you can download the mobile provisioning profile or access it in Xcode if you plan to build manually.
Now, if you want to automate signed builds using a cloud CI-CD provider, you need to make sure that these credentials are in your cloud environment. This can be tricky and will vary between CI-CD providers. You'll also need to update your signing config to file check if you're in a CI environment and then dynamically apply the signing credentials from your CI provider. This will also require some customization of your workflow file. Fortunately, AppFlow makes all this much easier. AppFlow is the mobile CI-CD platform built by Ionic. It handles your native iOS and Android builds in the cloud including the management of your signing credentials. You can use these credentials for on-demand builds or in automated workflows.
In the AppFlow dashboard, you simply upload your Android or your Apple credentials and you save them. Now, they can be used by any member of your team to generate signed builds. This makes it easy to identify different signing credentials used for development, ad hoc or app store build. The best part is you don't need to alter your React Native Gradle config. AppFlow takes care of that for you. You can select the signing credentials to use from the new build screen for an on-demand or from the automation screen when building out an automated workflow. AppFlow will create a cloud build environment to create native Android or iOS builds for your application.
For an on-demand build, start a new build by selecting which commit to use, then select a build target of either Android or iOS and the build stack. Select a build type and which signing credentials you want to use. And AppFlow also lets you optionally define custom environments or native configurations to use during the build. AppFlow will then create a build based on your specifications. The process is similar for automations. You create an automated workflow by specifying which branch to trigger the workflow when a new commit is pushed. Then, you'll configure the build that will kick off automatically for each commit. You can also automatically deploy to a set destination in the Apple App Store or the Google Play Store so your new build is ready to release.
If you'd like to learn more about mobile CICD and AppFlow, scan the QR code for a copy of our free e-book and contact us at appflow.ionic.io with any questions.
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
Workshops on related topic
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
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
Prerequisites
- 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
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.
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 goal.you 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 https://docs.expo.dev/get-started/create-a-new-app/
Comments