Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DeviceInfo native module is not installed correctly after updating to RN0.44.0 #176

Closed
georgest opened this issue May 10, 2017 · 8 comments

Comments

@georgest
Copy link

After updating React Native to 0.44.0 I get the error that DeviceInfo module is not installed correctly:

screen shot 2017-05-10 at 12 48 11 pm

"react": "^16.0.0-alpha.6",
"react-native": "^0.44.0",

@georgest
Copy link
Author

rm -rf node_modules && npm install is fixing the issue.

@moorthysubu
Copy link

rm -rf node_modules && npm doesn't seems works :(

@chrisbolin
Copy link

@moorthysubu I had to stop my iOS simulator as well as reinstall. then running react-native run-ios recompiled my project for the new version of RN

@chuckern
Copy link

I have the same issue.
And I run project at Xcode while have jsbundle in my project.
When I click Button and load the bundle that the simulator show this error.
I run rm -rf node_modules && npm install at rn root but does not work.
Please anyone can solve this problem help me.

@lucibit
Copy link

lucibit commented Jun 28, 2017

After doing all of the above and not working, I also uninstalled the app in my emulator (android uninstall by dragging it away) and recompiled (react-native run-android) and it worked!

@javayhu
Copy link

javayhu commented Jul 11, 2017

I have the same issue for both platforms, and the reason is that the version of RN libraries (integrates them into an old project) is not the same with the RN version used to build the bundle file. Check the versions if you have the same problem. :-)

@martsie
Copy link

martsie commented Oct 4, 2017

I had this issue because I had another react-native project open with its packager still running. Close that packager and rebuild the current project and all working again,

@gustavjf
Copy link

gustavjf commented Nov 6, 2017

Thanks @martsie, that was it for me.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

8 participants