Building Standalone Apps

The purpose of this guide is to help you create standalone binaries of your Expo app for iOS and Android which can be submitted to the Apple App Store and Google Play Store.

An Apple Developer account is needed to build an iOS standalone app, but a Google Play Developer account is not needed to build the Android standalone app. If you’d like to submit to either app store, you will need a developer account on that store.

It’s a good idea to read the best practices about Deploying to App Stores to ensure your app is in good shape to get accepted into the Apple and Google marketplaces. We can generate builds for you, but it’s up to you to make your app awesome.

1. Install exp

XDE currently doesn’t include an option for building a standalone app, so we’ll need exp for this. Run npm install -g exp to get it.

If you haven’t used exp before, the first thing you’ll need to do is login with your Expo account using exp login.

2. Configure app.json

   "expo": {
    "name": "Your App Name",
    "icon": "./path/to/your/app-icon.png",
    "version": "1.0.0",
    "slug": "your-app-slug",
    "sdkVersion": "XX.0.0",
    "ios": {
      "bundleIdentifier": "com.yourcompany.yourappname"
    "android": {
      "package": "com.yourcompany.yourappname"

The iOS bundleIdentifier and Android package fields use reverse DNS notation, but don’t have to be related to a domain. Replace "com.yourcompany.yourappname" with whatever makes sense for your app.

You’re probably not surprised that name, icon and version are required, but if you haven’t used Expo much you might be confused by slug and sdkVersion. slug is the url name that your app’s JavaScript is published to, for example, where community is my username and native-component-list is the slug. The sdkVersion tells Expo what Expo runtime version to use, which corresponds to a React Native version. Although "XX.0.0" is listed in the example, you already have an sdkVersion in your app.json and should not change it except when you want to update to a new version of Expo.

There are other options you might want to add to app.json. We have only covered what is required. For example, some people like to configure their own build number, linking scheme, and more. We highly recommend you read through Configuration with app.json for the full spec.

Note: iOS standalone apps default the status bar text color to white. But when developing within the Expo app, the default is black since the Expo app itself has a black status bar. Users are often surprised that their standalone apps suddenly have white status bars. In order to keep it black, you’ll need to use a <StatusBar barStyle="dark-content" /> component. See StatusBar docs for more information.

3. Start the build

Note for windows users, make sure you have WSL enabled. We recommend picking Ubuntu from the Windows Store, be sure to Launch Ubuntu at least once. Once you have that done, run in an Admin powershell: Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Windows-Subsystem-Linux

  • Run exp start in your app directory to boot up the Expo packager. This is necessary because during the build process your app will be republished to ensure it is the latest version.

  • Once the app has started, run exp build:android or exp build:ios.

If you choose to build for Android

The first time you build the project you will be asked whether you’d like to upload a keystore or have us handle it for you. If you don’t know what a keystore is, just leave it to us. Otherwise, feel free to upload your own.

[exp] No currently active or previous builds for this project.

Would you like to upload a keystore or have us generate one for you?
If you don't know what this means, let us handle it! :)

  1) Let Expo handle the process!
  2) I want to upload my own keystore!

Note: If you choose the first option and later decide to upload your own keystore, we currently offer an option to clear your current Android keystore from our build servers by running exp build:android --clear-credentials. This is irreversible, so only run this command if you know what you are doing! You can download a backup copy of the keystore by running exp fetch:android:keystore. If you do not have a local copy of your keystore , you will be unable to publish new versions of your app to the Play Store. Your only option would be to generate a new keystore and re-upload your application as a new application. You can learn more about how code signing and keystores work in the Android documentation.

If you choose to build for iOS

The first time you build the project, you will be prompted for your Apple ID and password for your developer account, and your Apple Team ID. This is needed to manage certificates and provisioning profiles, so we can build and send off push notifications.

[exp] No currently active or previous builds for this project.

We need your Apple ID/password to manage certificates and provisioning
profiles from your Apple Developer account.

What's your Apple ID?
Password? ******************
What is your Apple Team ID (you can find that on this page: XY1234567

Note: If your Apple id has two-factor authentication enabled, use the --local-auth flag (currently in beta).

Next we will ask you if you’d like us to handle your distribution certificate or use your own. Similar to the Android keystore, if you don’t know what a distribution certificate is, just let us handle it for you. If you do need to upload your own certificates, we recommend following this excellent guide on making a p12 file.

Note: The Expo build service supports both normal App Store distribution as well as enterprise distribution. To use the latter, you must be a member of the “Apple Developer Enterprise Program”. Only normal Apple developer accounts can build apps that can be submitted to the Apple App Store, and only enterprise developer accounts can build apps that can be distributed using enterprise distribution methods. During the build process, the Expo build service will detect the account type and select or create the correct type of distribution certificate and provisioning profile. At this time, the standalone app builder does not support “ad hoc” distribution certificates or provisioning profiles.

4. Wait for it to finish building

This will take a few minutes, you can check up on it by running exp build:status. When it’s done, you’ll see the url of a .apk (Android) or .ipa (iOS) file — this is your app. Copy and paste the link into your browser to download the file.

Note: We enable bitcode for iOS, so the .ipa files for iOS are much larger than the eventual App Store download available to your users. For more information, see App Thinning.

5. Test it on your device or simulator

  • You can drag and drop the .apk into your Android emulator. This is the easiest way to test out that the build was successful. But it’s not the most satisfying.

  • To run it on your Android device, make sure you have the Android platform tools installed along with adb, then just run adb install app-filename.apk with your device plugged in.

  • To test a device build with Apple TestFlight, download the .ipa file to your local machine. You are ready to upload your app to TestFlight. Within TestFlight, click the plus icon and create a New App. Make sure your bundleIdentifier matches what you’ve placed in exp.json.

Note: You will not see your build here just yet! You will need to use Xcode or Application Loader to upload your IPA first. Once you do that, you can check the status of your build under Activity. Processing an app can take 10-15 minutes before it shows up under available builds.

6. Submit it to the appropriate store

We don’t automate this step (yet), but at this point you should be able to follow the Apple and Google documentation to submit your standalone binary to each respective store. For more info on how to polish your app and ensure it is accepted to the Apple and Google marketplaces, read the guide on Deploying to App Stores.

7. Update your app

For the most part, when you want to update your app, just Publish again from exp or XDE. Your users will download the new JS the next time they open the app. To ensure your users have a seamless experience downloading JS updates, you may want to enable background JS downloads. However, there are a couple reasons why you might want to rebuild and resubmit the native binaries:

  • If you want to change native metadata like the app’s name or icon

  • If you upgrade to a newer sdkVersion of your app (which requires new native code)

To keep track of this, you can also update the binary’s versionCode and buildNumber. It is a good idea to glance through the app.json documentation to get an idea of all the properties you can change, e.g. the icons, deep linking url scheme, handset/tablet support, and a lot more.

If you run into problems during this process, we’re more than happy to help out! Join our Slack and let us know if you have any questions.