Development builds are the recommended setup for production
apps.
Initial Setup
If you don’t already have a project, create a new Expo app:- New Runtime (Recommended)
- Legacy Runtime
iOS Minimum Version
- New Runtime (Recommended)
- Legacy Runtime
The new runtime requires iOS 15.1 or later.If you’re using Expo SDK 52 or later, it already requires Option 1: Using
Continuous Native Generation (CNG) simplifies app maintenance and configuration by automatically generating your iOS and Android native projects using Prebuild.If you’re using CNG, you can set the minimum iOS deployment target directly in your
15.1 or later.If you’re using an older SDK, you’ll need to update your iOS deployment target manually or via configuration.Option 1: Using expo-build-properties (Recommended)
Continuous Native Generation (CNG) simplifies app maintenance and configuration by automatically generating your iOS and Android native projects using Prebuild.If you’re using CNG, you can set the minimum iOS deployment target directly in your app.json or app.config.js:Option 2: Manual Configuration
If you’re not using Prebuild, update the target directly in yourios/Podfile:Creating a Development Build
To run your app with the Rive runtime, you’ll need to create a development build. Since there are several ways to do this, refer to the Expo development builds guide to choose the method that best suits your needs.Running Your App
Once you’ve created a development build and installed it on your device or simulator, start your app with:- New Runtime (Recommended)
- Legacy Runtime
If you encounter errors loading the Rive file, make sure you’re running in a development build and not Expo Go.
Adding Local Assets
The example above loads a.riv file from a remote URL.
To use local .riv files, they must be bundled into your native build.
See Loading in Rive Files for instructions on working with local assets.