React-native: error: bundling: UnableToResolveError

Created on 5 May 2017 · 6Comments · Source: facebook/react-native

logcat info:
Loading dependency graph, done.
error: bundling: UnableToResolveError: Unable to resolve module react/lib/ReactDebugCurrentFrame from /Users/liuzipeng/Documents/AndroidWorkspace/ReactDemo/node_modules/react-native/Libraries/Renderer/src/renderers/shared/fiber/ReactFiberContext.js: Module does not exist in the module map or in these directories:
/Users/liuzipeng/Documents/AndroidWorkspace/ReactDemo/node_modules/react-native/node_modules/react/lib
, /Users/liuzipeng/Documents/AndroidWorkspace/ReactDemo/node_modules/react/lib

phone screen info:
Unable to download JS bundle

Locked

Source

550609334

Most helpful comment

using react-native-git-upgrade worked for me.

JulianKingman on 6 May 2017

🎉4 👍4

All 6 comments

i have the same issue :( on windows 7, react-native v0.44.0 react-native-router-flux v 3.38.0 react v15 node 6

chmiguel on 6 May 2017

👍1

+1
same issue, have config similar to @chmiguel

athaseen on 6 May 2017

using react-native-git-upgrade worked for me.

JulianKingman on 6 May 2017

🎉4 👍4

same problem，The solution?

zhangyao0328 on 18 May 2017

Npm i -g react-native-git-upgrade && react-native-git-upgrade

JulianKingman on 18 May 2017

👍6 🎉1

Hi there! This issue is being closed because it has been inactive for a while. Maybe the issue has been fixed in a recent release, or perhaps it is not affecting a lot of people. Either way, we're automatically closing issues after a period of inactivity. Please do not take it personally!

If you think this issue should definitely remain open, please let us know. The following information is helpful when it comes to determining if the issue should be re-opened:

Does the issue still reproduce on the latest release candidate? Post a comment with the version you tested.
If so, is there any information missing from the bug report? Post a comment with all the information required by the issue template.
Is there a pull request that addresses this issue? Post a comment with the PR number so we can follow up.

If you would like to work on a patch to fix the issue, contributions are very welcome! Read through the contribution guide, and feel free to hop into #react-native if you need help planning your contribution.