eas-update

13 notes, read out of this brain and free to use. Each one was extracted from a source and is re-checked against its exam.

expo-dev-client enables previewing published EAS Updates in development builds

The expo-dev-client library allows launching different versions of a project by creating a development build. Any compatible EAS Update can be previewed in a development build.

Prerequisites for previewing updates in development builds

To preview updates in a development build, you must have: (1) a development build installed on your device, Android Emulator, or iOS Simulator, and (2) the expo-updates library installed in your development build.

Extensions tab provides UI for previewing published updates

When using the expo-updates library inside a development build, the Extensions tab provides the ability to load and preview a published update automatically. After logging in to your Expo account within the development build, the Extensions tab displays the latest published updates for your project, and you can tap Open next to an update to preview it.

Steps to preview an update using Extensions tab

To preview an update using the Extensions tab: (1) Make non-native changes locally and publish them using eas update. (2) Open your development build, go to Extensions, and tap Login to log in to your Expo account. (3) After logging in, an EAS Update section will appear with published updates. Tap Open next to the update you want to preview.

View all published updates for a branch in Extensions tab

In the Extensions tab, you can view the list of all published updates for a branch by tapping the branch name.

Preview update via EAS dashboard

You can preview an update using the EAS dashboard by clicking the published update link in the CLI after running the eas update command. This opens the update's details on the Updates page. Click Preview to open a dialog where you can scan a QR code with your device's camera or select a platform to launch the update under Open with Orbit.

EAS Update deep link URL format for development builds

You can construct a specific URL to open an EAS Update in a development build with the format: [slug]://expo-development-client/?url=[https://u.expo.dev/project-id]/group/[group-id]. Example: my-app://expo-development-client/?url=https://u.expo.dev/675cb1f0-fa3c-11e8-ac99-6374d9643cb2/group/47839bf2-9e01-467b-9378-4a978604ab11. Copy and paste the URL into the development build's launcher screen under Enter URL Manually, or create a QR code and scan it with your device's camera.

EAS Update deep link URL components

The EAS Update deep link URL has these components: (1) [slug] - the project's slug found in the app config; (2) ://expo-development-client/ - necessary for the deep link to work with expo-dev-client; (3) ?url= - defines a url query parameter; (4) https://u.expo.dev/[project-id] - the updates URL from the project's app config under updates.url; (5) /group/[group-id] - the group ID of the update.

Updates.isEmbeddedLaunch property usage

The Updates.isEmbeddedLaunch property returns true if the currently running update is embedded in the build, and false if it was downloaded from the server. Use this property to determine whether an update can be traced in the EAS dashboard, since embedded updates are not tracked in the dashboard.

Updates.updateId behavior with embedded launches

Updates.updateId always returns an ID regardless of whether Updates.isEmbeddedLaunch is true or false. However, if the app is running an embedded update, attempting to look up the updateId in the EAS dashboard will result in an error because embedded updates are not tracked in the dashboard.

Tracing update ID in EAS dashboard URL structure

To navigate to a specific platform update in the EAS dashboard, use the URL format: https://expo.dev/accounts/[accountName]/projects/[projectName]/updates/[updateId]. Replace updateId with the value from Updates.updateId to open the corresponding update group for the platform-specific update.

Example: Display update embedded status

This example shows how to display whether the currently running update is embedded or downloaded: ```tsx import * as Updates from 'expo-updates'; import { Text } from 'react-native'; export default function UpdateStatus() { return ( <Text> {Updates.isEmbeddedLaunch ? '(Embedded) ❌ You cannot trace this update in the EAS dashboard.' : '(Downloaded) ✅ You can trace this update in the EAS dashboard.'} </Text> ); } ```

expo-asset remove Classic Updates support

Support for the Classic Updates service was removed for SDK 50. References to the Classic Updates CDN were removed. Applications must migrate to EAS Update or other services that conform to the modern Expo Updates protocol.

Give your agent this brain