Using in a managed Expo Workflow

[gowedixyz]

I was wondering if this could be used within Expo or if expo eject is needed. I'm having some troubles integrating this into an expo react native project using development builds (as opposed to expo go). Particularly:

iOS Bundled 30949ms node_modules/expo-router/entry.js (1800 modules)
 ERROR  Invariant Violation: `new NativeEventEmitter()` requires a non-null argument., js engine: hermes 
    at ContextNavigator (http://192.168.1.7:8081/node_modules/expo-router/entry.bundle//&platform=ios&dev=true&hot=false&lazy=true&transform.engine=hermes&transform.bytecode=true&transform.routerRoot=src%2Fapp:149946:24)
    at ExpoRoot (http://192.168.1.7:8081/node_modules/expo-router/entry.bundle//&platform=ios&dev=true&hot=false&lazy=true&transform.engine=hermes&transform.bytecode=true&transform.routerRoot=src%2Fapp:149902:28)
    at App
    at ErrorToastContainer (http://192.168.1.7:8081/node_modules/expo-router/entry.bundle//&platform=ios&dev=true&hot=false&lazy=true&transform.engine=hermes&transform.bytecode=true&transform.routerRoot=src%2Fapp:300373:24)
    at ErrorOverlay
    at withDevTools(ErrorOverlay) (http://192.168.1.7:8081/node_modules/expo-router/entry.bundle//&platform=ios&dev=true&hot=false&lazy=true&transform.engine=hermes&transform.bytecode=true&transform.routerRoot=src%2Fapp:299876:27)
    at RCTView
    at View (http://192.168.1.7:8081/node_modules/expo-router/entry.bundle//&platform=ios&dev=true&hot=false&lazy=true&transform.engine=hermes&transform.bytecode=true&transform.routerRoot=src%2Fapp:41520:43)
    at RCTView
    at View (http://192.168.1.7:8081/node_modules/expo-router/entry.bundle//&platform=ios&dev=true&hot=false&lazy=true&transform.engine=hermes&transform.bytecode=true&transform.routerRoot=src%2Fapp:41520:43)
    at AppContainer (http://192.168.1.7:8081/node_modules/expo-router/entry.bundle//&platform=ios&dev=true&hot=false&lazy=true&transform.engine=hermes&transform.bytecode=true&transform.routerRoot=src%2Fapp:41363:25)
    at main(RootComponent) (http://192.168.1.7:8081/node_modules/expo-router/entry.bundle//&platform=ios&dev=true&hot=false&lazy=true&transform.engine=hermes&transform.bytecode=true&transform.routerRoot=src%2Fapp:119719:28)

Is there a workaround?

[vojtapohunek]

Hi, did you get it to run eventually? We're facing the same problem. It seems Circle is not maintaining this at all :(

[Frexuz]

ye, zero effort from their side, even after multiple emails back and forth
we ended up implementing a webview and deploy a separate tiny nextjs app with the web sdk

like whats the point? just delete this repo instead of giving up hope, and spending time implementing something that doesn't work