react-native: [iOS] Simulator error message `Unable to find module for DevLoadingView`

@superguineapig I just hit this too. Fixed by going to the simulator menu and hitting Hardware > Erase All Content and Settings... then Hardware > Restart. Hardware restart might not be necessary…I think the simulator restarts anyway after clearing stuff.

Now I’ve got a new error to solve about a missing Pod 😃, but thats specific to my project.

Same here on 0.60.4.

Getting this on RN58.4 - pretty annoying.

Seems like a bug in RN 0.58.3, I’m seeing this in a freshly created project.

This should be fixed with this commit: https://github.com/facebook/react-native/commit/a9dd828c68338dbf0e55ffa1838bf8ff574f317d – will be picked to the RC branches

I got it to work as well. All I had to do was disable the remote debugger.

When the simulator failed, I opened the tools with Command + D and disabled the debugger.

I’ve managed to resolve the red box by making this change: https://github.com/karanjthakkar/ReactNativeDevLoadingViewIssue/commit/e1a637cd82bf45e6af6814746d863b131b76ac62

NOTE: THIS IS A HACK. It only works for 0.59.0-rc.0 and upwards. That is because they use initWithDelegate to initialise the RN bridge.

For folks on an older version(<= 0.58), please do these two things:

1. Replace your AppDelegate.m with this file: https://github.com/facebook/react-native/blob/da5b5d2fa134aa09dda4a620be9fa4d3d419201f/template/ios/HelloWorld/AppDelegate.m. After replacing, remember to update the moduleName from HelloWorld to whatever is there in your app.json
2. Replace your AppDelegate.h file by this one: https://github.com/facebook/react-native/blob/da5b5d2fa134aa09dda4a620be9fa4d3d419201f/template/ios/HelloWorld/AppDelegate.h NOTE: If you’re replacing any files, make sure you copy any custom code you added to it in the past.

Why this fix works?

By returning YES from the bridge:didNotFindModule method, it enters the if condition here instead of going to the else condition where it runs into the error.

Still seeing it on 0.60.4

@fkgozali I’m still seeing this issue on real device (ios), with react native 0.59.3. It must be something else going on.

@dongcaiying Yes, after refreshing it on the error screen it works. But then you have to refresh 2 times. This answer on stack overflow solved the issue for me.

+1 Same error on 0.60.4

Issue occurring here also. React Native 0.59.8 (Expo SDK 33), with iOS on iPhone (not simulator). Reloading the bundle works, but on reload after a change this comes up sporadically.

This is happening as a part of the latest 0.59.0-rc1 as well.

Steps to reproduce:

1. Init a project with react-native init
2. Run in simulator/device
3. Once RN screen loads, enabled JS debugging
4. (IMPORTANT) Close the app
5. Open the app again
6. You will see the redbox error

The error for the redbox was added in https://github.com/facebook/react-native/commit/d7a0c44590bcf3fb9d055aeae3391d5bcd7e21be but that in itself is a part of a series of commits for lazy loading native modules by @fkgozali.

Note: This error is non blocking. iiuc, you can dismiss the red box and your RN screen will still be loaded behind it.

@kelset Do you have any ideas how we can get this issue resolved?

Awesome, good luck with your Pod hunt!

For those building to a device: I had the same issue on my iPhone (XR) rather than in simulator, solution was to delete the app through the phone and then re-trust the developer in Settings > General > Device Management.

First time encountered this after upgrading from 0.59.10 to 0.60.4. In my case it happens when I try to refresh (⌘ + R) iOS simulator.

Thanks for reporting this, I’ve flagged this as something we should address before 0.59 hits stable.

The same issue on a real device. Seems like an application starts before js bundle is created

@algera You can disable it, then re-enable it. It would appear it just needs to be toggled off when you’re starting up.

@samcorcos how am i suppose to disable the disable the debugger?