I appear to have gotten myself into a bit of a quandary. I have been running my app with the remote debugger enabled for months. Now when I run it without remote debugging, I get this error:
2020-09-09 19:37:35.890 [info][tid:main][RCTCxxBridge.mm:1037] Invalidating <RCTCxxBridge: 0x7ff17c4477a0> (parent: <RCTBridge: 0x600001f41b20>, executor: (null))2020-09-09 19:37:35.891 [info][tid:main][RCTCxxBridge.mm:213] Initializing <RCTCxxBridge: 0x7ff17c793670> (parent: <RCTBridge: 0x600001f41b20>, executor: (null))2020-09-09 19:37:36.644 [error][tid:com.facebook.react.JavaScript] Exception in HostObject::set: Unable to put on NativeModules: Operation unsupported2020-09-09 19:37:36.645 [fatal][tid:com.facebook.react.ExceptionsManagerQueue] Unhandled JS Exception: Exception in HostObject::set: Unable to put on NativeModules: Operation unsupported2020-09-09 19:37:36.664 [info][tid:main][RCTRootView.m:293] Running application vepo ({ initialProps = { }; rootTag = 161;})2020-09-09 19:37:36.665 [info][tid:com.facebook.react.JavaScript] Running application "vepo" with appParams: {"rootTag":161,"initialProps":{}}. __DEV__ === true, development-level warning are ON, performance optimizations are OFF2020-09-09 19:37:36.665 [error][tid:com.facebook.react.JavaScript] Application vepo has not been registered.Hint: This error often happens when you're running the packager (local dev server) from a wrong folder. For example you have multiple apps and the packager is still running for the app you were working on before.If this is the case, simply kill the old packager instance (e.g. close the packager terminal window) and start the packager in the correct app folder (e.g. cd into app folder and run 'npm start').This error can also happen due to a require() error during initialization or failure to call AppRegistry.registerComponent.2020-09-09 19:37:36.668 [fatal][tid:com.facebook.react.ExceptionsManagerQueue] Unhandled JS Exception: Application vepo has not been registered.Hint: This error often happens when you're running the packager (local dev server) from a wrong folder. For example you have multiple apps and the packager is still running for the app you were working on before.If this is the case, simply kill the old packager instance (e.g. close the packager terminal window) and start the packager in the correct app folder (e.g. cd into app folder and run 'npm start').This error can also happen due to a require() error during initialization or failure to call AppRegistry.registerComponent.2020-09-09 19:37:36.669 [info][tid:com.facebook.react.JavaScript] 'BugReporting extraData:', { 'AppRegistry.runApplication1': 'Running application "vepo" with appParams: {"rootTag":161,"initialProps":{}}. __DEV__ === true, development-level warning are ON, performance optimizations are OFF' }2020-09-09 19:37:36.670 [info][tid:com.facebook.react.JavaScript] 'BugReporting extraData:', { 'AppRegistry.runApplication1': 'Running application "vepo" with appParams: {"rootTag":161,"initialProps":{}}. __DEV__ === true, development-level warning are ON, performance optimizations are OFF' }2020-09-09 19:37:36.670 [info][tid:com.facebook.react.JavaScript] 'BugReporting extraData:', { 'AppRegistry.runApplication1': 'Running application "vepo" with appParams: {"rootTag":161,"initialProps":{}}. __DEV__ === true, development-level warning are ON, performance optimizations are OFF' }2020-09-09 19:37:39.692 [info][tid:com.facebook.react.JavaScript] 'BugReporting extraData:', { 'AppRegistry.runApplication1': 'Running application "vepo" with appParams: {"rootTag":161,"initialProps":{}}. __DEV__ === true, development-level warning are ON, performance optimizations are OFF' }2020-09-09 19:37:41.589 [info][tid:com.facebook.react.JavaScript] 'BugReporting extraData:', { 'AppRegistry.runApplication1': 'Running application "vepo" with appParams: {"rootTag":161,"initialProps":{}}. __DEV__ === true, development-level warning are ON, performance optimizations are OFF' }Obviously I have now learnt from this to test regularly without remote debugging. Looking online, most people with this error have to add a dependency to their android build.gradle. However, I'm not developing for Android, I'm only developing for iOS. I assume it's an equivalent issue where I have to add some dependency for iOS somewhere. But I have no idea what package is the one causing this issue. What can I do to debug this error? Is there some more detailed error message I can get from Xcode? Or find out what dependency it is attempting to read when it errors? I'm not using cocoapods for my dependencies.