Expo publish not working with SDK 44

Expo Development Tools
1

We have migrated some projects to SDK 44 and app updates via expo publish are no longer being installed. Seems also related to eas-cli versions. Anyone have similar problems?

Here’s a summary:

// this configuration works
SDK 43
eas-cli : 0.34.1
expo-cli : 5.0.3

// this configuration does not work
SDK 44
eas-cli : 0.42.4 (latest)
expo-cli : 5.0.3

2

Have you already solved it? I’ve got the same issue with a new app based on SDK 44 and i used EAS.

3

Hi - I ended up reverting to 43…, hoping that others may have a solution

4

Facing same problem. Did you find any solution.

5

Seeing the same thing, has anyone found a fix? Android OTA works fine, but can’t get iOS to update through expo publish.

6

Experiencing the same thing after upgrading to Expo 44. Seeing the following errors in prod being reported by Sentry:

  1. The updates module controller has not been properly initialized. If you’re in development mode, you cannot check for updates. Otherwise, make sure you have called [[EXUpdatesAppController sharedInstance] start].

  2. Error: Failed to download manifest from URL: ****

“expo”: “44.0.0”,
“expo-updates”: “~0.11.6”,

@notbrent any ideas?

7

can you provide more information about your project? run expo diagnostics and tell me how you are building it

8 
System:
      OS: macOS 11.6
      Shell: 5.8 - /bin/zsh
    Binaries:
      Node: 16.13.1 - /usr/local/bin/node
      Yarn: 1.22.17 - /opt/homebrew/bin/yarn
      npm: 8.1.2 - /usr/local/bin/npm
      Watchman: 2021.11.15.00 - /opt/homebrew/bin/watchman
    Managers:
      CocoaPods: 1.11.2 - /usr/local/bin/pod
    SDKs:
      iOS SDK:
        Platforms: DriverKit 21.2, iOS 15.2, macOS 12.1, tvOS 15.2, watchOS 8.3
      Android SDK:
        API Levels: 29, 30
        Build Tools: 29.0.2, 29.0.3
        System Images: android-29 | Android TV Intel x86 Atom, android-29 | Intel x86 Atom, android-29 | Intel x86 Atom_64, android-29 | Google APIs Intel x86 Atom, android-29 | Google APIs Intel x86 Atom_64, android-29 | Google Play ARM 64 v8a, android-29 | Google Play Intel x86 Atom, android-29 | Google Play Intel x86 Atom_64, android-30 | Android TV Intel x86 Atom, android-30 | China version of Wear OS 3 - Preview Intel x86 Atom, android-30 | Wear OS 3 - Preview Intel x86 Atom, android-30 | Intel x86 Atom_64, android-30 | Google TV Intel x86 Atom, android-30 | Google APIs Intel x86 Atom, android-30 | Google APIs Intel x86 Atom_64, android-30 | Google Play Intel x86 Atom, android-30 | Google Play Intel x86 Atom_64
        Android NDK: 22.1.7171670
    IDEs:
      Android Studio: 2020.3 AI-203.7717.56.2031.7784292
      Xcode: 13.2.1/13C100 - /usr/bin/xcodebuild
    npmPackages:
      expo: ^44.0.0 => 44.0.6 
      react: 17.0.1 => 17.0.1 
      react-dom: 17.0.1 => 17.0.1 
      react-native: 0.64.3 => 0.64.3 
      react-native-web: 0.17.1 => 0.17.1 
      react-navigation: ^4.3.9 => 4.4.4 
    npmGlobalPackages:
      eas-cli: 0.52.0
      expo-cli: 5.3.0
    Expo Workflow: bare

I’m building it with expo publish command

9

It was working fine with SDK 43. Is it related to the Constants.installationId being deprecated in sdk 44 ?

10

@notbrent do i need to start using eas publish instead of expo publish ?

11

nope, EAS Update is entirely opt-in. you can continue to use “Classic” updates (expo publish) just fine. i’ll share this with the updates team to see if they have any ideas. meanwhile, would you be able to create a minimal reproducible example project?

12

Facing same problem. Did you find any solution?