---
title: Debug EAS Update
sidebar_title: Basic
description: Learn how to debug EAS Update.
---

import ImageSpotlight from '~/components/plugins/ImageSpotlight';
import { Terminal } from '~/ui/components/Snippet';

This guide shows how to verify our configuration so that we can find the source of problems like an app not showing a published update. It's important to tell the current state of our app at any given time, so EAS Update was built with this in mind. Once we know which updates are running on which builds, we can make changes so that our apps are in the state we expect.

> If we are not using EAS Build, our Deployments page will be empty. Follow the guide on [debugging configuration without EAS Build](/eas-update/debug-advanced/#configuration-without-eas-build) instead.

## Go to the Deployments page

The EAS website has a [Deployments page](https://expo.dev/accounts/[account]/projects/[project]/deployments) that shows the current state of our app. The term _deployment_ refers to a group of builds and their corresponding updates. If we've made builds and updates with EAS, we can see our project's status on the website in the Deployments tab.

<ImageSpotlight
  alt="Deployments tab"
  src="/static/images/eas-update/deployments-website-tab.png"
  style={{ maxWidth: 400 }}
/>

## Common problems

The following section describes common problems and how to fix them. Below is a diagram of how EAS Update works and the spots that are useful to inspect when finding the root cause of an issue. In the following sections, we'll inspect and verify these spots and more.

<ImageSpotlight alt="Map of debugging spots" src="/static/images/eas-update/debug-map.png" />

### Unexpected channel

<ImageSpotlight
  alt="Deployment has unexpected channel"
  src="/static/images/eas-update/deployments-wrong-channel.png"
  style={{ maxWidth: 600 }}
/>

If the deployment channel is unexpected, it means our build was not built with the correct channel. To fix this, [configure our channel](/#configure-channel) and rebuild our app.

### Unexpected runtime version

<ImageSpotlight
  alt="Deployment has unexpected runtime version"
  src="/static/images/eas-update/deployments-wrong-runtime.png"
  style={{ maxWidth: 600 }}
/>

If the deployment runtime version is unexpected, it means our build was not built with the correct runtime version. To fix this, [configure our runtime version](/#configure-runtime-version) and rebuild our app.

### Unexpected branch

<ImageSpotlight
  alt="Deployment has unexpected branch"
  src="/static/images/eas-update/deployments-wrong-branch.png"
  style={{ maxWidth: 600 }}
/>

If the deployment has an unexpected branch, we need to [map our channel to the correct branch](/#map-channel-to-branch).

### Missing updates

<ImageSpotlight
  alt="Deployment has no updates"
  src="/static/images/eas-update/deployments-no-updates.png"
  style={{ maxWidth: 600 }}
/>

The displayed deployment does not have any updates. To fix this, [publish an update to the branch](/#publish-update). If an update was already published, check the [Updates page](https://expo.dev/accounts/[account]/projects/[project]/updates) to make sure it matches the runtime version of our build.

### Missing branch

<ImageSpotlight
  alt="Deployment has no branch"
  src="/static/images/eas-update/deployments-no-branch.png"
  style={{ maxWidth: 600 }}
/>

The displayed deployment has the correct channel, but it is not linked to a branch. To fix this, [map the channel to the correct branch](/#map-channel-to-branch).

### Missing deployment

If our deployment is not displayed, it means our build is not configured properly for EAS Update. To fix this, [configure our channel](/#configure-channel), [configure our runtime version](/#configure-runtime-version) and verify our [general configuration](/debug-advanced/#verifying-app-configuration). We'll need to rebuild our app after making these changes.

## Solutions

### Configure channel

To verify that a build has a specific channel, make sure our build profile in **eas.json** has a channel property:

```json eas.json
{
  "build": {
    "preview": {
      "distribution": "internal",
      "channel": "preview"
    },
    "production": {
      "channel": "production"
    }
  }
}
```

Then, we can run a command like `eas build --profile preview` to create a build with a channel named "preview".

### Configure runtime version

To verify our runtime version, we make sure our app config (**app.json**/**app.config.js**) has a `runtimeVersion` property:

```json app.json
{
  "expo": {
    "runtimeVersion": {
      "policy": "sdkVersion"
    }
  }
}
```

By default, it is `{ "policy": "sdkVersion" }`, but we can change our runtime to [use a different policy or a specific version](/eas-update/runtime-versions). Then, we can run a command like `eas build --profile preview` to create a build with the runtime version we expect.

### Map channel to branch

If the channel is not mapped to the branch we expect, we can change the link with:

<Terminal
  cmd={[
    '# eas channel:edit [channel-name] --branch [branch-name]',
    '',
    '',
    '# Example',
    'eas channel:edit production --branch release-1.0',
  ]}
/>

If our branch is not listed, we can create a new branch with `eas branch:create`.

### Publish update

To create and publish an update, we can run the following command:

<Terminal cmd={['$ eas update']} />

After publishing, the output will display the branch and the runtime version. This information can help us verify that we're creating an update with the configuration we expect.

## Next steps

Read the [advanced guide](/eas-update/debug-advanced) to debug EAS Update when the basic steps don't resolve your issue.