infinitered / ignite

Infinite Red's battle-tested React Native project boilerplate, along with a CLI, component/model generators, and more!
MIT License
17.59k stars 1.39k forks source link

init project run ios #2797

Closed hoangcuong22 closed 1 week ago

hoangcuong22 commented 1 week ago

Describe the bug

Invariant Violation: TurboModuleRegistry.getEnforcing(...): 'DevMenu' could not be found. Verify that a module by this name is registered in the native binary.Bridgeless mode: false. TurboModule interop: false. Modules loaded: {"NativeModules":["PlatformConstants","LogBox","Timing","AppState","SourceCode","BlobModule","WebSocketModule","SettingsManager","DevSettings","RedBox","Networking","Appearance","DevLoadingView","UIManager","DeviceInfo","ImageLoader","LinkingManager","RNGestureHandlerModule","I18nManager","AsyncLocalStorage"],"TurboModules":[],"NotFound":["NativePerformanceCxx","NativePerformanceObserverCxx","BugReporting","HeadlessJsTaskSupport","SoundManager","IntentAndroid","PlatformLocalStorage","RNC_AsyncSQLiteDBStorage","RNCAsyncStorage","AsyncSQLiteDBStorage","DevMenu"]}, js engine: hermes

Ignite version

"9.10.1"

Additional info

{B8F04DE9-A3AB-4264-9BAF-C77B51354A6D}

hoangcuong22 commented 1 week ago

help me

theBulmad commented 1 week ago

This DevMenu issue is becoming quite common now, I'm experiencing the same when attempting to use expo go.

hoangcuong22 commented 1 week ago

I had this problem when running the app on iOS but Android worked fine

hoangcuong22 commented 1 week ago

Do you have any way to solve it?

theBulmad commented 1 week ago

@hoangcuong22 try this: yarn expo prebuild -p ios cd ios && pod install yarn ios

Found it in the ignite slack channel

TokenAce commented 1 week ago

Same issue here with new project - Expo Go is a no Go

frankcalise commented 1 week ago

Previous discussion around the same issue in https://github.com/infinitered/ignite/issues/2678

Couple of things you can do here:

  1. Remove the offending Reactotron custom command here
  2. Utilize Expo CNG
  3. Go with npx ignite-cli@next (which will use CNG) which should be released this week

But this will not be fixed here as it's related to Expo Go