eas updates not getting installed

I’m having trouble with automatic updates in SDK47 using managed workflow

(my eas-cli version is eas-cli/3.13.2)

Following the debugging guide Debugging EAS Update - Expo Documentation all seems well until Proxyman investigations where it says I should be getting requests made to https://u.expo.dev and https://assets.eascdn.net. I’m getting two made to https://u.expo.dev but none to https://assets.eascdn.net

I do get a warning from the Configure expo-updates section of the build log…
This build is configured to query EAS Update for updates, however no channel is set in eas.json.

but an eas channel:view production seems to suggest all is well…

Name production
ID 277e6386-474b-4aee-a571-d7389e12c14f

Branches pointed at this channel and their most recent update group:

Branch production
Platforms android, ios
Runtime Version exposdk:47.0.0
Message “Testing eas updates” (22 hours ago by buxtonfringe)
Group ID f0f5110a-dfcb-45fb-ae12-92b3e6ee85c0

my app.json has…


   "extra": {
      "eas": {
        "projectId": "cc213070-a6c7-11e8-9de4-df07f8f19bfc"
    "runtimeVersion": {
      "policy": "sdkVersion"

my eas.json is…

  "cli": {
    "version": ">= 2.4.1"
  "build": {
    "development": {
      "developmentClient": true,
      "distribution": "internal"
    "preview": {
      "distribution": "internal"
    "production": {}
  "submit": {
    "production": {}

Any suggestions on how to get successful calls made to https://assets.eascdn.net would be gratefully received.



Adding a channel: “production” setting to the production build in eas.json has done the trick and eas updates now get delivered to devices :slight_smile:

However, I’d be interested to know how to configure a managed app so that Proxyman can intercept requests. From step 5 of Android Device & Emulator - Proxyman Documentation I need to add a network_security_config.xml file to the build and then reference it in the AndroidManifest.xml file…

<?xml version="1.0" encoding="utf-8"?>
<manifest ... >
    <application android:networkSecurityConfig="@xml/network_security_config" ... >

Debugging EAS Update - Expo Documentation has a screenshot that showing that seeing the response content must be possible but maybe only on a bare project?