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'.

Local path or remote URL to an image to display while starting up the app. Image size and aspect ratio are up to you. Must be a .png.

If no icon is provided, we will show the Expo logo. You can choose between white and blue.

Similar to exponentIconColor but instead indicate if it should be grayscale (1) or not (0).

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.

Color to fill the loading screen background

By default, Expo shows some text at the bottom of the loading screen. Set this to true to disable.

@deprecated Previously used for changing the style of the iOS loading indicator.

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

Specifies whether the status bar should be translucent (whether it should be treated as a block element that will take up space on the device's screen and limit space available for the rest of your app to be rendered, or be treated as an element with 'position = absolute' that is rendered above your app's content). Defaults to true (default iOS behavior, the iOS status bar cannot be set translucent by the system)

Determines how and when the navigation bar is shown. Learn more. 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.

If set to false, your standalone app will never download any code, and will only use code bundled locally on the device. In that case, all updates to your app must be submitted through Apple review. Defaults to true. (Note: This will not work out of the box with ExpoKit projects)

By default, Expo 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. Must be one of ON_LOAD or ON_ERROR_RECOVERY

How long (in ms) to allow for fetching OTA updates before falling back to a cached version of the app. Defaults to 30000 (30 sec). Must be between 0 and 300000 (5 minutes).

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.

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.

Merchant ID for use with Apple Pay in your standalone 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.

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.

@deprecated Use updates.enabled instead.

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

@deprecated Use updates key with fallbackToCacheTimeout: 0 instead.

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 true currently, but will change to false in a future SDK version.

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.

An array that contains Associated Domains for the standalone app. See Apple's docs for config.

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.

If set to true, APK will contain only unimodules that are explicitly added in package.json and their dependencies

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 an 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.

A Boolean value that indicates whether the app should use the new notifications API.

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.

List of permissions used by the standalone app.

To use ONLY the following minimum necessary permissions and none of the extras supported by Expo in a default managed app, set permissions to []. The minimum necessary permissions do not require a Privacy Policy when uploading to Google Play Store and are: • receive data from Internet • view network connections • full network access • change your audio settings • prevent device from sleeping

To use ALL permissions supported by Expo by default, do not specify the permissions key.

To use the minimum necessary permissions ALONG with certain additional permissions, specify those extras in permissions, e.g.

[ "CAMERA", "ACCESS_FINE_LOCATION" ].

You can specify the following permissions depending on what you need:

• ACCESS_COARSE_LOCATION
• ACCESS_FINE_LOCATION
• ACCESS_BACKGROUND_LOCATION
• CAMERA
• RECORD_AUDIO
• READ_CONTACTS
• WRITE_CONTACTS
• READ_CALENDAR
• WRITE_CALENDAR
• READ_EXTERNAL_STORAGE
• WRITE_EXTERNAL_STORAGE
• USE_FINGERPRINT
• USE_BIOMETRIC
• WRITE_SETTINGS
• VIBRATE
• READ_PHONE_STATE
• com.anddoes.launcher.permission.UPDATE_COUNT
• com.android.launcher.permission.INSTALL_SHORTCUT
• com.google.android.c2dm.permission.RECEIVE
• com.google.android.gms.permission.ACTIVITY_RECOGNITION
• com.google.android.providers.gsf.permission.READ_GSERVICES
• com.htc.launcher.permission.READ_SETTINGS
• com.htc.launcher.permission.UPDATE_SHORTCUT
• com.majeur.launcher.permission.UPDATE_BADGE
• com.sec.android.provider.badge.permission.READ
• com.sec.android.provider.badge.permission.WRITE
• com.sonyericsson.home.permission.BROADCAST_BADGE

Firebase Configuration File Location of the GoogleService-Info.plist 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.

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

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.

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.