question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Error: package expo.loaders.provider.interfaces does not exist (update from SDK 36 to 37)

See original GitHub issue

🐛 Bug Report

Environment

Expo CLI 3.15.5 environment info:
    System:
      OS: Linux 5.3 Pop!_OS 18.04 LTS
      Shell: 5.4.2 - /usr/bin/zsh
    Binaries:
      Node: 10.19.0 - /usr/bin/node
      Yarn: 1.22.4 - /usr/bin/yarn
      npm: 6.13.4 - /usr/bin/npm
    npmPackages:
      expo: ^37.0.0 => 37.0.3 
      react: 16.9.0 => 16.9.0 
      react-native: https://github.com/expo/react-native/archive/sdk-37.0.0.tar.gz => 0.61.4 
      react-navigation: ^3.1.4 => 3.11.1 

Project is in ExpoKit already updated to SDK 37 also

Steps to Reproduce

Update from SDK 36 to SDK 37

Expected Behavior

Android build without issues

Actual Behavior

android/app/src/main/java/host/exp/exponent/MainApplication.java:10: error: package expo.loaders.provider.interfaces does not exist
import expo.loaders.provider.interfaces.AppLoaderPackagesProviderInterface;
                                       ^
android/app/src/main/java/host/exp/exponent/MainApplication.java:27: error: cannot find symbol
public class MainApplication extends ExpoApplication implements AppLoaderPackagesProviderInterface<ReactPackage> {
                                                                ^
  symbol: class AppLoaderPackagesProviderInterface
2 errors 

Issue Analytics

  • State:closed
  • Created 3 years ago
  • Comments:5 (2 by maintainers)

github_iconTop GitHub Comments

5reactions
Andrea-Arguellocommented, Apr 1, 2020

Solved by changing the import MainApplication.java of my project

- import expo.loaders.provider.interfaces.AppLoaderPackagesProviderInterface;
+ import org.unimodules.apploader.AppLoaderPackagesProviderInterface;
1reaction
Andrea-Arguellocommented, Apr 2, 2020

Regarding my previous comment, this is something I noticed that was deleted from the MainApplication.java from SDK 36 to SDK 37. So, this is either a bug that needs to be fixed, or intentional and needs to be added to the upgrading documentation, as noted on #7574 . Therefore, I am leaving this issue open.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Expo 45 build fail on Android with EAS
I've upgraded the SDK version to 45 recently. Everything works well except it doesn't build either on Android or IO.
Read more >
React - error: package expo.modules.updates does not exist
I had a similar issue and found that there was a BasePackageList.java file that contained these references. Deleting the file solved it.
Read more >
expo-modules-core:compiledebugjavawithjavac - You.com
My error is like this (it's with Expo but the error can change to ... error: package android.content.pm does not exist import android.content.pm....
Read more >
expo-cli | Yarn - Package Manager
The command-line tool for creating and publishing Expo apps ... Changelog. This is the log of notable changes to Expo CLI and related...
Read more >
Expo SDK 37 is now available - DEV Community ‍ ‍
Update the Expo app on your phones from the App Store / Google Play. expo-cli will automatically update your apps in simulators if...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found