Enabling Remote JS Debugging consistently crashes app

Please provide the following:

  1. SDK Version:39
  2. Platforms(Android/iOS/web/all): Android

Note: I have tried to enable “Debug Remote JS” with a bare minimum project (expo init) and still face the same issue.

I have an issue that only occurs after I enable “Debug Remote JS” in my Expo App. I am able to load the app on my device using expo start, or build an apk and load that using expo build:android. Both of these work fine, but when I decide to enable Debug Remote JS, my app will always crash immediately. This occurs on both my physical device (Motorola One Action) and my emulated Pixel 3

ADB Logcat shows this stack trace:

09-29 16:16:52.922  2092  2229 E Expo    : Cannot initialize app loader. host.exp.exponent.taskManager.ExpoHeadlessAppLoader
09-29 16:16:52.922  2092  2229 W System.err: java.lang.ClassNotFoundException: host.exp.exponent.taskManager.ExpoHeadlessAppLoader
09-29 16:16:52.927  2092  2229 W System.err: 	at java.lang.Class.classForName(Native Method)
09-29 16:16:52.927  2092  2229 W System.err: 	at java.lang.Class.forName(Class.java:454)
09-29 16:16:52.927  2092  2229 W System.err: 	at java.lang.Class.forName(Class.java:379)
09-29 16:16:52.927  2092  2229 W System.err: 	at l.d.a.a.a(AppLoaderProvider.java:2)
09-29 16:16:52.927  2092  2229 W System.err: 	at l.d.a.a.b(AppLoaderProvider.java:2)
09-29 16:16:52.927  2092  2229 W System.err: 	at expo.modules.taskManager.TaskService.getAppLoader(TaskService.java:2)
09-29 16:16:52.927  2092  2229 W System.err: 	at expo.modules.taskManager.TaskService.isStartedByHeadlessLoader(TaskService.java:1)
09-29 16:16:52.927  2092  2229 W System.err: 	at expo.modules.taskManager.TaskService.setTaskManager(TaskService.java:2)
09-29 16:16:52.928  2092  2229 W System.err: 	at expo.modules.taskManager.TaskManagerInternalModule.onCreate(TaskManagerInternalModule.java:5)
09-29 16:16:52.928  2092  2229 W System.err: 	at l.d.b.f.h(ModuleRegistry.java:9)
09-29 16:16:52.928  2092  2229 W System.err: 	at l.d.b.f.a(ModuleRegistry.java:2)
09-29 16:16:52.928  2092  2229 W System.err: 	at org.unimodules.adapters.react.ModuleRegistryReadyNotifier.initialize(ModuleRegistryReadyNotifier.java:1)
09-29 16:16:52.930  2092  2229 W System.err: 	at com.facebook.react.bridge.ModuleHolder.doInitialize(ModuleHolder.java:9)
09-29 16:16:52.931  2092  2229 W System.err: 	at com.facebook.react.bridge.ModuleHolder.markInitializable(ModuleHolder.java:7)
09-29 16:16:52.931  2092  2229 W System.err: 	at com.facebook.react.bridge.NativeModuleRegistry.notifyJSInstanceInitialized(NativeModuleRegistry.java:5)
09-29 16:16:52.931  2092  2229 W System.err: 	at com.facebook.react.bridge.CatalystInstanceImpl$4.run(CatalystInstanceImpl.java:1)
09-29 16:16:52.931  2092  2229 W System.err: 	at android.os.Handler.handleCallback(Handler.java:938)
09-29 16:16:52.932  2092  2229 W System.err: 	at android.os.Handler.dispatchMessage(Handler.java:99)
09-29 16:16:52.932  2092  2229 W System.err: 	at com.facebook.react.bridge.queue.MessageQueueThreadHandler.dispatchMessage(MessageQueueThreadHandler.java:1)
09-29 16:16:52.932  2092  2229 W System.err: 	at android.os.Looper.loop(Looper.java:223)
09-29 16:16:52.932  2092  2229 W System.err: 	at com.facebook.react.bridge.queue.MessageQueueThreadImpl$4.run(MessageQueueThreadImpl.java:8)
09-29 16:16:52.932  2092  2229 W System.err: 	at java.lang.Thread.run(Thread.java:923)
09-29 16:16:52.932  2092  2229 W System.err: Caused by: java.lang.ClassNotFoundException: host.exp.exponent.taskManager.ExpoHeadlessAppLoader
09-29 16:16:52.932  2092  2229 W System.err: 	... 22 more

I have googled and found that someone removed their splash screen import, but I do not use splash screen in my app. I am not sure how to debug this error.

A longer logcat is available at https://pastebin.com/arGqjkHH

This is my package.json

{
  "main": "node_modules/expo/AppEntry.js",
  "scripts": {
    "start": "expo start",
    "android": "expo start --android",
    "ios": "expo start --ios",
    "web": "expo start --web",
    "eject": "expo eject"
  },
  "dependencies": {
    "@ptomasroos/react-native-multi-slider": "^2.2.2",
    "@react-native-community/async-storage": "~1.12.0",
    "@react-native-community/masked-view": "0.1.10",
    "@react-navigation/bottom-tabs": "^5.8.0",
    "@react-navigation/drawer": "^5.9.0",
    "@react-navigation/material-bottom-tabs": "^5.2.16",
    "@react-navigation/native": "^5.7.3",
    "@react-navigation/stack": "^5.9.0",
    "axios": "^0.20.0",
    "expo": "^39.0.3",
    "expo-linear-gradient": "~8.3.0",
    "expo-updates": "~0.3.3",
    "react": "16.13.1",
    "react-dom": "16.13.1",
    "react-native": "0.63.2",
    "react-native-animatable": "^1.3.3",
    "react-native-deck-swiper": "^2.0.5",
    "react-native-flags": "^1.0.0",
    "react-native-gesture-handler": "~1.7.0",
    "react-native-maps": "0.27.1",
    "react-native-paper": "^4.1.0",
    "react-native-reanimated": "~1.13.0",
    "react-native-safe-area-context": "3.1.4",
    "react-native-screens": "~2.10.1",
    "react-native-unimodules": "~0.11.0",
    "react-native-vector-icons": "^7.1.0",
    "react-native-web": "~0.13.7",
    "react-redux": "^7.2.1",
    "redux": "^4.0.5",
    "redux-persist": "^6.0.0",
    "use-state-with-callback": "^2.0.3"
  },
  "devDependencies": {
    "@babel/core": "~7.9.0",
    "babel-jest": "~25.2.6",
    "jest": "~25.2.6",
    "react-test-renderer": "~16.11.0",
    "reactotron-react-native": "^5.0.0",
    "reactotron-redux": "^3.1.3"
  },
  "private": true
}

If you need any other information, I can provide it. I am trying to debug my redux store so any help is greatly appreciated

For what it’s worth. I found this thread which indicated the problem was in SDK 39.

When I downgraded to SDK 38. my issues were resolved.

Yes, as per that thread it’s a known issue. It looks like the fixes have been merged, so I expect the fix will be released soon.

The fix for this has apparently been released:

This topic was automatically closed 20 days after the last reply. New replies are no longer allowed.