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

UnableToResolveError: Unable to resolve module ActivityIndicator #15256 #15289

Closed
ferminmoli opened this issue Jul 31, 2017 · 7 comments
Closed
Labels
Stale There has been a lack of activity on this issue and it may be closed soon.

Comments

@ferminmoli
Copy link

error: bundling: UnableToResolveError: Unable to resolve module ActivityIndicator from C:\Projects\node_modules\react-native\Libraries\react-native\react-native-implementation.js: Module does not exist in the module map or in these directories:
C:\Projects\node_modules\react-native\node_modules
, C:\Projects\node_modules

react-native -v: 0.44.3
node -v: 6.10
npm -v: 3.10.10
Target Platform: Android
Development Operating System: Windows 10
Build tools: Android SDK 23
Step to reproduce:
1 - react-native run-android

NOTE: The following steps did not work for me

Clear watchman watches: watchman watch-del-all.
Delete the node_modules folder: rm -rf node_modules && npm install.
Reset packager cache: rm -fr $TMPDIR/react-* or npm start -- --reset-cache.
Clone repository from the scratch and install modules again

@hramos
Copy link
Contributor

hramos commented Jul 31, 2017

The latest version is 0.46.4, have you tried that? This error sounds like something we fixed already.

@ferminmoli
Copy link
Author

Yes, I tried it, but it did not work.

@hramos
Copy link
Contributor

hramos commented Jul 31, 2017

Did you recently upgrade react-native? This can happen if there's a disconnect between the versions used in the native app and JavaScript.

@BrunoBernardino
Copy link

BrunoBernardino commented Aug 10, 2017

Seems like a duplicate of #14209.

I also just recently started having this issue (upgrading from 0.46.4 to 0.47.1) and going back isn't helping.

@jnrepo
Copy link

jnrepo commented Aug 22, 2017

updated from 0.42.3 to 0.47.1 and I'm getting this error...

@iMokhles
Copy link

#15671 i was facing this issue also and fixed it with other issues and posted my fix here

@stale
Copy link

stale bot commented Oct 26, 2017

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Maybe the issue has been fixed in a recent release, or perhaps it is not affecting a lot of people. If you think this issue should definitely remain open, please let us know why. Thank you for your contributions.

@stale stale bot added the Stale There has been a lack of activity on this issue and it may be closed soon. label Oct 26, 2017
@stale stale bot closed this as completed Nov 2, 2017
@facebook facebook locked and limited conversation to collaborators May 15, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Stale There has been a lack of activity on this issue and it may be closed soon.
Projects
None yet
Development

No branches or pull requests

5 participants