updates.url: a URL of a remote service implementing the Expo Updates protocol

The example updates URL and projectId shown below are used with EAS Update. The EAS CLI sets this URL correctly for the EAS Update service when running eas update:configure. If you want to set up a custom expo-updates server instead, add your URL to updates.url in app.json.

You can override the update URL and request headers at runtime using the Updates.setUpdateURLAndRequestHeadersOverride() method. This can be useful if you want to load a specific update or change the update channel while the app is running. Learn more. The details page for an update (for example: https://expo.dev/accounts/[account]/projects/[project]/updates/[id]) shows metrics for the number of users who have run the update, in addition to the number of failed installs (users who download and attempted to run the update, but it crashed).

The feature described in this section is available in Expo SDK 52 with the expo-updates version 0.27.0 and later. Using the disableAntiBrickingMeasures option is not recommended for production apps, it is currently primarily intended for preview environments. Similar to override request headers, if you want to further override the update URL to a specific update, you can use the Updates.setUpdateURLAndRequestHeadersOverride method.

The URL will look like the following: ... [slug]://expo-development-client/?url=[https://u.expo.dev/project-id]/group/[group-id] # Examplemy-app://expo-development-client/?url=https://u.expo.dev/675cb1f0-fa3c-11e8-ac99-6374d9643cb2/group/47...

```xml <?xml version="1.0" ... <string>YOUR-APP-URL-HERE</string> </dict> </plist> ``` EXUpdatesURL is the remote URL at which your app will be hosted, and to which expo-updates will query for new updates....

February 16, 2022 - { "expo": { "name": "ota-app", "slug": "ota-app", "version": "1.0.4", "orientation": "portrait", "icon": "./assets/icon.png", "splash": { "image": "./assets/splash.png", "resizeMode": "contain", "backgroundColor": "#ffffff" }, "updates": { "fallbackToCacheTimeout": 300000, "url" : "https://stevemoretz.github.io/expo-ota-app/" }, "assetBundlePatterns": [ "**/*" ], "ios": { "supportsTablet": true, "bundleIdentifier": "com.stevemoretz.otaapp" }, "android": { "adaptiveIcon": { "foregroundImage": "./assets/adaptive-icon.png", "backgroundColor": "#FFFFFF" } }, "web": { "favicon": "./assets/favicon.png" } } }

The EXPO_UPDATE_URL value should contain your project's ID.

<meta-data android:name="expo.modules.updates.EXPO_UPDATE_URL" android:value="https://your-url-to-access-config/android-index.json" /> <meta-data android:name="expo.modules.updates.EXPO_RUNTIME_VERSION" android:value="1.0.0" />

Update updates.url in app.json and re-run the build steps below. The example Expo project configured for the server is located in /expo-updates-client.

If no updates URL is specified, the owner and the slug fields will be used to generate one: https://exp.host/@${owner}/${slug}. It can also be set by passing a URL to the --public-url flag of the expo export command.

The EAS Update hosted service implements this protocol. To build a custom server that implements the protocol, see the example server source code here. ... Learn how to install expo-updates in your project in the Installing expo-updates documentation page.

Inside our project's app config (app.json/app.config.json), the URL we can GET is under updates.url. This url is EAS' "https://u.expo.dev" domain, followed by the project's ID on EAS servers. If we go to the URL directly, we'll see an error ...

September 12, 2024 - I'm looking to add OTA Updates to my React Native application, but I want to implement my own server (I'm not paying the official expo way to deliver OTA updates), but I encountered the issue that the eas update command doesn't allow me to upload the update to my server and requires me to modify the value of expo.updates.url to a expo server link.

To get your project's ID, use the URL in the app config's expo.updates.url field.

In my case I had ios/<AppName>/Supporting/Expo.plist. I tried setting the EXUpdatesEnabled key to false, but the app still crashed with this error. I did notice I did not have a key for EXUpdatesURL so I added one with a fake value of https://example.com and that step worked for me. My app now loads correctly. ... ok after investigating I found the reason why , the update url is put in the android manifest generated by expo eject ONLY if you have done expo login before , so adding a expo login step before solved my issue Read more comments on GitHub >

January 4, 2021 - 🐛 Bug Report I created a project with expo,but want to eject it. everthing looks very well,but i run the project in xcode,finally,it report "expo-updates must be configured with a valid update URL or scope key" package.json { "scripts": ...

May 12, 2025 - The EXPO_UPDATE_URL value should contain your project's ID.

November 30, 2023 - Expo Updates is a library from Expo that allows developers to instantly push app updates and changes to their in-testing (think TestFlight) or in-production app. It’s a part of the Expo ecosystem, which simplifies the React Native development process.

Modify android/app/src/main/AndroidManifest.xml to add the expo-updates configuration XML so that it matches the contents of app.json: If using the updates server URL (a custom non-HTTPS update server running on the same machine), you will need to modify android/app/src/main/AndroidManifest.xml to add the update server URL and enable usesCleartextTraffic: