Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

[iOS] Simulator error message `Unable to find module for DevLoadingView`

See original GitHub issue

Environment

React Native Environment Info: System: OS: macOS High Sierra 10.13.6 CPU: x64 Intel® Core™ i7-7820HQ CPU @ 2.90GHz Memory: 2.85 GB / 16.00 GB Shell: 3.2.57 - /bin/bash Binaries: Node: 8.10.0 - ~/.nvm/versions/node/v8.10.0/bin/node Yarn: 1.13.0 - /usr/local/bin/yarn npm: 5.6.0 - ~/.nvm/versions/node/v8.10.0/bin/npm Watchman: 4.9.0 - /usr/local/bin/watchman SDKs: iOS SDK: Platforms: iOS 12.1, macOS 10.14, tvOS 12.1, watchOS 5.1 Android SDK: Build Tools: 23.0.1, 25.0.2, 25.0.3, 26.0.1, 26.0.2, 27.0.1, 27.0.3, 28.0.2, 28.0.3 API Levels: 23, 25, 26, 27 IDEs: Android Studio: 3.1 AI-173.4907809 Xcode: 10.1/10B61 - /usr/bin/xcodebuild npmPackages: react: 16.6.3 => 16.6.3 react-native: 0.58.3 => 0.58.3 npmGlobalPackages: react-native-git-upgrade: 0.2.7

Description

Recently upgraded to RN 0.58.3 (from 0.57.8) via react-native-git-upgrade. Everything compiles just fine.

However, invoking a debug run via react-native run-ios will result in an immediate error message:

Notes:

Reloads (cmd-R) of a running app clear the error. (App runs as expected)
Subsequent reloads (cmd-R) of already running app do not trigger the error. (App runs as expected)
Closing either the simulator itself and restarting, OR closing the running app within the simulator session and relaunching will trigger the error once again.
Each of the 0.58.0, 0.58.1, 0.58.2, 0.58.3 releases give the same results.

Reproducible Demo

In my case it was simply upgrading to RN 0.58.3 from 0.57.8 via react-native-git-upgrade then running react-native run-ios to encounter the error message.

Issue Analytics

State:
Created 5 years ago
Reactions:61
Comments:31 (7 by maintainers)

Top GitHub Comments

62reactions

snobearcommented, Feb 1, 2019

@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.

17reactions

adanmayercommented, Jul 29, 2019

Same here on 0.60.4.