Expo Updates

useUpdateEvents(listener)

React hook to create an UpdateEvent listener subscription on mount, using addListener. It calls remove() on the subscription during unmount.

function App() {
  const eventListener = (event) => {
    if (event.type === Updates.UpdateEventType.ERROR) {
      // Handle error
    } else if (event.type === Updates.UpdateEventType.NO_UPDATE_AVAILABLE) {
      // Handle no update available
    } else if (event.type === Updates.UpdateEventType.UPDATE_AVAILABLE) {
      // Handle update available
    }
  };
  Updates.useUpdateEvents(eventListener);
  // React Component...
}

Updates.checkForUpdateAsync()

Checks the server to see if a newly deployed update to your project is available. Does not actually download the update. This method cannot be used in development mode, and the returned promise will be rejected if you try to do so.

Checking for an update uses a device's bandwidth and battery life like any network call. Additionally, updates served by Expo may be rate limited. A good rule of thumb to check for updates judiciously is to check when the user launches or foregrounds the app. Avoid polling for updates in a frequent loop.

Updates.clearLogEntriesAsync()

Clears existing expo-updates log entries.

For now, this operation does nothing on the client. Once log persistence has been implemented, this operation will actually remove existing logs.

Updates.fetchUpdateAsync()

Downloads the most recently deployed update to your project from server to the device's local storage. This method cannot be used in development mode, and the returned promise will be rejected if you try to do so.

Updates.getExtraParamsAsync()

Retrieves the current extra params.

Updates.readLogEntriesAsync(maxAge)

Retrieves the most recent expo-updates log entries.

Updates.reloadAsync()

Instructs the app to reload using the most recently downloaded version. This is useful for triggering a newly downloaded update to launch without the user needing to manually restart the app.

It is not recommended to place any meaningful logic after a call to await Updates.reloadAsync(). This is because the promise is resolved after verifying that the app can be reloaded, and immediately before posting an asynchronous task to the main thread to actually reload the app. It is unsafe to make any assumptions about whether any more JS code will be executed after the Updates.reloadAsync method call resolves, since that depends on the OS and the state of the native module and main threads.

This method cannot be used in development mode, and the returned promise will be rejected if you try to do so.

Updates.setExtraParamAsync(key, value)

Sets an extra param if value is non-null, otherwise unsets the param. Extra params are sent in a header of update requests. The update server may use these params when evaluating logic to determine which update to serve. EAS Update merges these params into the fields used to evaluate channel–branch mapping logic.

Updates.addListener(listener)

Adds a callback to be invoked when updates-related events occur (such as upon the initial app load) due to auto-update settings chosen at build-time. See also the useUpdateEvents React hook.