SDK 45 Beta 8 [Android] Cannot access expo.modules.updatesinterface.UpdatesInterface

Summary

After running expo upgrade to SDK 45 beta 8, the same line of code here in MainApplication.java onCreate() method:

if (BuildConfig.DEBUG) {
    DevLauncherController.getInstance().setUpdatesInterface(UpdatesDevLauncherController.initialize(this));
}

is giving a new error:

Cannot access expo.modules.updatesinterface.UpdatesInterface

I have already tried Invalidating Caches, cleaning and rebuilding the project to no avail. Reverted back to SDK 44 and it immediately started working again.

Managed or bare workflow? If you have ios/ or android/ directories in your project, the answer is bare!

bare

What platform(s) does this occur on?

Android

SDK Version (managed workflow only)

SDK 45 beta-8

Environment

expo-env-info 1.0.3 environment info:
    System:
      OS: macOS 12.4
      Shell: 5.8.1 - /bin/zsh
    Binaries:
      Node: 16.15.0 - ~/.nvm/versions/node/v16.15.0/bin/node
      Yarn: 1.22.18 - ~/.yarn/bin/yarn
      npm: 8.5.5 - ~/.nvm/versions/node/v16.15.0/bin/npm
      Watchman: 2022.03.21.00 - /opt/homebrew/bin/watchman
    Managers:
      CocoaPods: 1.11.3 - /opt/homebrew/bin/pod
    SDKs:
      iOS SDK:
        Platforms: DriverKit 21.4, iOS 15.4, macOS 12.3, tvOS 15.4, watchOS 8.5
      Android SDK:
        API Levels: 29, 30, 31, 32
        Build Tools: 29.0.2, 30.0.2, 30.0.3, 31.0.0
        System Images: android-31 | Google APIs ARM 64 v8a
        Android NDK: 21.4.7075529
    IDEs:
      Xcode: 13.3.1/13E500a - /usr/bin/xcodebuild
    npmPackages:
      expo: ^45.0.0-beta.8 => 45.0.0-beta.8 
      react: 17.0.2 => 17.0.2 
      react-native: 0.68.1 => 0.68.1 
    Expo Workflow: bare

Reproducible demo

@Override
public void onCreate() {
    super.onCreate();
    // If you opted-in for the New Architecture, we enable the TurboModule system
    ReactFeatureFlags.useTurboModules = BuildConfig.IS_NEW_ARCHITECTURE_ENABLED;
    SoLoader.init(this, /* native exopackage */ false);
    DevLauncherController.initialize(this, getReactNativeHost());
    if (BuildConfig.DEBUG) {
        DevLauncherController.getInstance().setUpdatesInterface(UpdatesDevLauncherController.initialize(this));
    }
    initializeFlipper(this, getReactNativeHost().getReactInstanceManager());
    ApplicationLifecycleDispatcher.onApplicationCreate(this);
}

[thespacemanatee]

@mackenziekira @byCedric not sure if this is the proper workaround but this code works instead: DevLauncherUpdatesInterfaceDelegate.INSTANCE.initializeUpdatesInterface(this); and seems to do the same thing as: DevLauncherController.getInstance().setUpdatesInterface(UpdatesDevLauncherController.initialize(this)); which is currently not working (Cannot access expo.modules.updatesinterface.UpdatesInterface)

EDIT: Side note, the past few releases of Expo SDKs tend to have breaking changes that are not listed in the changelog and documentation is usually not updated even after a few months. The recent fiasco with expo-notifications is another example. Is this symptomatic of the Expo team not testing SDKs thoroughly with each release? We use these services in production and some of us even pay big money to Expo so stability is something that’s really important to us.

[thespacemanatee]

@thespacemanatee did you find a workaround for this? I am running into it too

I just left it commented out. Looking at the method signature, I don’t think it does much? Especially since it only runs on debug releases. Perhaps the documentation is outdated and this is no longer needed @byCedric