Expo SDK

(Android only) Local path or remote URL to an image to use as the icon for push notifications. 96x96 png grayscale with transparency. We recommend following Google's design guidelines. If not provided, defaults to your app icon.

(Android only) Tint color for the push notification image when it appears in the notification tray. Defaults to #ffffff

Whether or not to display notifications when the app is in the foreground on iOS. _displayInForeground option in the individual push notification message overrides this option. Learn more. Defaults to false.

Show each push notification individually (default) or collapse into one (collapse).

If androidMode is set to collapse, this title is used for the collapsed notification message. For example, '#{unread_notifications} new interactions'.

Configures the status bar icons to have a light or dark color. Valid values: light-content, dark-content. Defaults to dark-content

Specifies the background color of the status bar. Defaults to #00000000 (transparent) for dark-content bar style and #00000088 (semi-transparent black) for light-content bar style

Instructs the system whether the status bar should be visible or not. Defaults to false

When false, the system status bar pushes the content of your app down (similar to position: relative). When true, the status bar floats above the content in your app (similar to position: absolute). Defaults to true to match the iOS status bar behavior (which can only float above content). Explicitly setting this property to true will add android:windowTranslucentStatus to styles.xml and may cause unexpected keyboard behavior on Android when using the softwareKeyboardLayoutMode set to resize. In this case you will have to use KeyboardAvoidingView to manage the keyboard layout.

Determines how and when the navigation bar is shown. Learn more. Requires expo-navigation-bar be installed in your project. Valid values: leanback, immersive, sticky-immersive

leanback results in the navigation bar being hidden until the first touch gesture is registered.

immersive results in the navigation bar being hidden until the user swipes up from the edge where the navigation bar is hidden.

sticky-immersive is identical to 'immersive' except that the navigation bar will be semi-transparent and will be hidden again after a short period of time.

Configure the navigation bar icons to have a light or dark color. Supported on Android Oreo and newer. Valid values: 'light-content', 'dark-content'

Specifies the background color of the navigation bar.

If true, the app will launch in a development client with no additional dialogs or progress indicators, just like in a standalone app.

Whether the updates system will run. Defaults to true. If set to false, builds will only use code and assets bundled at time of build.

By default, expo-updates will check for updates every time the app is loaded. Set this to ON_ERROR_RECOVERY to disable automatic checking unless recovering from an error. Set this to NEVER to disable automatic checking. Valid values: ON_LOAD (default value), ON_ERROR_RECOVERY, WIFI_ONLY, NEVER

Whether to load the embedded update. Defaults to true. If set to false, an update will be fetched at launch. When set to false, ensure that checkAutomatically is set to ON_LOAD and fallbackToCacheTimeout is large enough for the initial remote update to download. This should not be used in production.

How long (in ms) to wait for the app to check for and fetch a new update upon launch before falling back to the most recent update already present on the device. Defaults to 0. Must be between 0 and 300000 (5 minutes). If the startup update check takes longer than this value, any update downloaded during the check will be applied upon the next app launch.

URL from which expo-updates will fetch update manifests

Local path of a PEM-formatted X.509 certificate used for verifying codesigned updates. When provided, all updates downloaded by expo-updates must be signed.

Metadata for codeSigningCertificate

Extra HTTP headers to include in HTTP requests made by expo-updates when fetching manifests or assets. These may override preset headers.

Array of glob patterns specifying which files should be included in updates. Glob patterns are relative to the project root. A value of ['**'] will match all asset files within the project root. When not supplied all asset files will be included. Example: Given a value of ['app/images/**/*.png', 'app/fonts/**/*.woff'] all .png files in all subdirectories of app/images and all .woff files in all subdirectories of app/fonts will be included in updates.

Color to fill the loading screen background

Determines how the image will be displayed in the splash loading screen. Must be one of cover or contain, defaults to contain.

Local path or remote URL to an image to fill the background of the loading screen. Image size and aspect ratio are up to you. Must be a .png.

The Apple development team ID to use for all native targets. You can find your team ID in the Apple Developer Portal.

The manifest for the iOS version of your app will be written to this path during publish.

The bundle for the iOS version of your app will be written to this path during publish.

The bundle identifier for your iOS standalone app. You make it up, but it needs to be unique on the App Store. See this StackOverflow question.

Build number for your iOS standalone app. Corresponds to CFBundleVersion and must match Apple's specified format. (Note: Transporter will pull the value for Version Number from expo.version and NOT from expo.ios.buildNumber.)

The background color for your iOS app, behind any of your React views. Overrides the top-level backgroundColor key if it is present. Requires expo-system-ui be installed in your project to work on iOS.

Local path or remote URL to an image to use for your app's icon on iOS. If specified, this overrides the top-level icon key. Use a 1024x1024 icon which follows Apple's interface guidelines for icons, including color profile and transparency.

Expo will generate the other required sizes. This icon will appear on the home screen and within the Expo app.

URL to your app on the Apple App Store, if you have deployed it there. This is used to link to your store page from your Expo project page if your app is public.

Enable iOS Bitcode optimizations in the native build. Accepts the name of an iOS build configuration to enable for a single configuration and disable for all others, e.g. Debug, Release. Not available in Expo Go. Defaults to undefined which uses the template's predefined settings.

Note: This property key is not included in the production manifest and will evaluate to undefined. It is used internally only in the build process, because it contains API keys that some may want to keep private.

Firebase Configuration File Location of the GoogleService-Info.plist file for configuring Firebase.

Whether your standalone iOS app supports tablet screen sizes. Defaults to false.

If true, indicates that your standalone iOS app does not support handsets, and only supports tablets.

If true, indicates that your standalone iOS app does not support Slide Over and Split View on iPad. Defaults to false

Configuration to force the app to always use the light or dark user-interface appearance, such as "dark mode", or make it automatically adapt to the system preferences. If not provided, defaults to light.

Dictionary of arbitrary configuration to add to your standalone app's native Info.plist. Applied prior to all other Expo-specific configuration. No other validation is performed, so use this at your own risk of rejection from the App Store.

Dictionary of arbitrary configuration to add to your standalone app's native *.entitlements (plist). Applied prior to all other Expo-specific configuration. No other validation is performed, so use this at your own risk of rejection from the App Store.

Dictionary of privacy manifest definitions to add to your app's native PrivacyInfo.xcprivacy file. Learn more

An array that contains Associated Domains for the standalone app. Learn more.

A boolean indicating if the app uses iCloud Storage for DocumentPicker. See DocumentPicker docs for details.

A boolean indicating if the app uses Apple Sign-In. See AppleAuthentication docs for details.

A Boolean value that indicates whether the app may access the notes stored in contacts. You must receive permission from Apple before you can submit your app for review with this capability.

Configuration for loading and splash screen for standalone iOS apps.

Specifies the JavaScript engine for iOS apps. Supported only on EAS Build. Defaults to hermes. Valid values: hermes, jsc.

A Boolean value that indicates whether the iOS app should use the new architecture.

Property indicating compatibility between an iOS build's native code and an OTA update for the iOS platform. If provided, this will override the value of the top level runtimeVersion key on iOS.

The manifest for the Android version of your app will be written to this path during publish.

The bundle for the Android version of your app will be written to this path during publish.

The package name for your Android standalone app. You make it up, but it needs to be unique on the Play Store. See this StackOverflow question.

Version number required by Google Play. Increment by one for each release. Must be a positive integer. Learn more

The background color for your Android app, behind any of your React views. Overrides the top-level backgroundColor key if it is present.

Configuration to force the app to always use the light or dark user-interface appearance, such as "dark mode", or make it automatically adapt to the system preferences. If not provided, defaults to light. Requires expo-system-ui be installed in your project to work on Android.

Local path or remote URL to an image to use for your app's icon on Android. If specified, this overrides the top-level icon key. We recommend that you use a 1024x1024 png file (transparency is recommended for the Google Play Store). This icon will appear on the home screen and within the Expo app.

Settings for an Adaptive Launcher Icon on Android. Learn more

URL to your app on the Google Play Store, if you have deployed it there. This is used to link to your store page from your Expo project page if your app is public.

A list of permissions to add to the app AndroidManifest.xml during prebuild. For example: ['android.permission.SCHEDULE_EXACT_ALARM']

List of permissions to block in the final AndroidManifest.xml. This is useful for removing permissions that are added by native package AndroidManifest.xml files which are merged into the final manifest. Internally this feature uses the tools:node="remove" XML attribute to remove permissions. Not available in Expo Go.

Firebase Configuration File Location of the google-services.json file for configuring Firebase. Including this key automatically enables FCM in your standalone app.

Note: This property key is not included in the production manifest and will evaluate to undefined. It is used internally only in the build process, because it contains API keys that some may want to keep private.

Configuration for loading and splash screen for managed and standalone Android apps.

Configuration for setting an array of custom intent filters in Android manifest. Learn more

Allows your user's app data to be automatically backed up to their Google Drive. If this is set to false, no backup or restore of the application will ever be performed (this is useful if your app deals with sensitive information). Defaults to the Android default, which is true.

Determines how the software keyboard will impact the layout of your application. This maps to the android:windowSoftInputMode property. Defaults to resize. Valid values: resize, pan.

Specifies the JavaScript engine for Android apps. Supported only on EAS Build and in Expo Go. Defaults to hermes. Valid values: hermes, jsc.

A Boolean value that indicates whether the Android app should use the new architecture.

Property indicating compatibility between a Android build's native code and an OTA update for the Android platform. If provided, this will override the value of top level runtimeVersion key on Android.

Sets the export method for the web app for both expo start and expo export. static statically renders HTML files for every route in the app/ directory, which is available only in Expo Router apps. single outputs a Single Page Application (SPA), with a single index.html in the output folder, and has no statically indexable HTML. server outputs static HTML, and API Routes for hosting with a custom Node.js server. Defaults to single.

Relative path of an image to use for your app's favicon.

Defines the title of the document, defaults to the outer level name

A short version of the app's name, 12 characters or fewer. Used in app launcher and new tab pages. Maps to short_name in the PWA manifest.json. Defaults to the name property.

Specifies the primary language for the values in the name and short_name members. This value is a string containing a single language tag.

Defines the navigation scope of this website's context. This restricts what web pages can be viewed while the manifest is applied. If the user navigates outside the scope, it returns to a normal web page inside a browser tab/window. If the scope is a relative URL, the base URL will be the URL of the manifest.

Defines the color of the Android tool bar, and may be reflected in the app's preview in task switchers.

Provides a general description of what the pinned website does.

Specifies the primary text direction for the name, short_name, and description members. Together with the lang member, it helps the correct display of right-to-left languages.

Defines the developers’ preferred display mode for the website.

The URL that loads when a user launches the application (e.g., when added to home screen), typically the index. Note: This has to be a relative URL, relative to the manifest URL.

Defines the default orientation for all the website's top level browsing contexts.

Defines the expected “background color” for the website. This value repeats what is already available in the site’s CSS, but can be used by browsers to draw the background color of a shortcut when the manifest is available before the stylesheet has loaded. This creates a smooth transition between launching the web application and loading the site's content.

If content is set to default, the status bar appears normal. If set to black, the status bar has a black background. If set to black-translucent, the status bar is black and translucent. If set to default or black, the web content is displayed below the status bar. If set to black-translucent, the web content is displayed on the entire screen, partially obscured by the status bar.

Hints for the user agent to indicate to the user that the specified native applications (defined in expo.ios and expo.android) are recommended over the website.

Experimental features. These will break without deprecation notice.

Configuration for PWA splash screens.

Firebase web configuration. Used by the expo-firebase packages on both web and native. Learn more

Sets the bundler to use for the web platform. Only supported in the local CLI npx expo. Defaults to webpack if the @expo/webpack-config package is installed, if not, it defaults to metro.

Export a website relative to a subpath of a domain. The path will be prepended as-is to links to all bundled resources. Prefix the path with a / (recommended) to load all resources relative to the server root. If the path does not start with a / then resources will be loaded relative to the code that requests them, this could lead to unexpected behavior. Example '/subpath'. Defaults to '' (empty string).

If true, indicates that this project does not support tablets or handsets, and only supports Apple TV and Android TV

Enable tsconfig/jsconfig compilerOptions.paths and compilerOptions.baseUrl support for import aliases in Metro.

Enable support for statically typed links in Expo Router. This feature requires TypeScript be set up in your Expo Router v2 project.

Enables Turbo Modules, which are a type of native modules that use a different way of communicating between JS and platform code. When installing a Turbo Module you will need to enable this experimental option (the library still needs to be a part of Expo SDK already, like react-native-reanimated v2). Turbo Modules do not support remote debugging and enabling this option will disable remote debugging.

Experimentally use a vendored canary build of React for testing upcoming features.

Experimentally enable React Compiler.

Experimentally enable React Server Components support in Expo CLI and Expo Router.

List of plugins already run on the config