react-native: Haste module overrides for react-native-windows resolution failures
- Review the documentation: https://facebook.github.io/react-native
- Search for existing issues: https://github.com/facebook/react-native/issues
- Use the latest React Native release: https://github.com/facebook/react-native/releases
Environment
Run react-native info
in your terminal and paste its contents here.
React Native Environment Info:
System:
OS: macOS High Sierra 10.13.3
CPU: x64 Intel(R) Core(TM) i7-7820HQ CPU @ 2.90GHz
Memory: 90.15 MB / 16.00 GB
Shell: 3.2.57 - /bin/bash
Binaries:
Node: 8.9.4 - /usr/local/bin/node
Yarn: 1.7.0 - /usr/local/bin/yarn
npm: 6.1.0 - /usr/local/bin/npm
SDKs:
iOS SDK:
Platforms: iOS 11.4, macOS 10.13, tvOS 11.4, watchOS 4.3
Android SDK:
Build Tools: 23.0.1, 25.0.3, 26.0.2, 27.0.3
API Levels: 23, 25, 27
IDEs:
Android Studio: 3.0 AI-171.4443003
Xcode: 9.4.1/9F2000 - /usr/bin/xcodebuild
npmPackages:
react: 16.3.2 => 16.3.2
react-native: 0.56.0-rc.1 => 0.56.0-rc.1
npmGlobalPackages:
react-native-cli: 2.0.1
Description
Describe your issue in detail. Include screenshots if needed. If this is a regression, let us know.
react-native-windows
overrides haste modules in react-native
, currently using the @providesModule
attribute. For example, the ScrollView
module in react-native
has behavior that limits it to iOS and Android, we we override the module in react-native-windows
here.
Prior to react-native
0.56.0 RC (which moved to metro
0.38), this behavior worked as expected. Now, the haste module overrides for windows no longer seem to get resolved. Specifically, I get the following error:
Unable to resolve module `AccessibilityInfo` from `/Users/rozele/code/sandbox/v56/node_modules/react-native/Libraries/react-native/react-native-implementation.js`: Module `AccessibilityInfo` does not exist in the Haste module map
This might be related to https://github.com/facebook/react-native/issues/4968
To resolve try the following:
1. Clear watchman watches: `watchman watch-del-all`.
2. Delete the `node_modules` folder: `rm -rf node_modules && npm install`.
3. Reset Metro Bundler cache: `rm -rf /tmp/metro-bundler-cache-*` or `npm start -- --reset-cache`. 4. Remove haste cache: `rm -rf /tmp/haste-map-react-native-packager-*`.
Please note - the AccessibiltyInfo
module just happens to be the first module in the dependency graph that we provide a *.windows.js
override for, so it has nothing to do with that module specifically.
Reproducible Demo
Let us know how to reproduce the issue. Include a code sample, share a project, or share an app that reproduces the issue using https://snack.expo.io/. Please follow the guidelines for providing a MCVE: https://stackoverflow.com/help/mcve
A very simple test that repos (on both Windows and Mac):
- Generate a new react-native project with 0.56.0-rc.4:
react-native init test --version 0.56.0-rc.4
- Generate a react-native-windows project:
yarn add rnpm-plugin-windows
react-native windows --windowsVersion 0.55.0-rc.0
- Try to generate a windows platform bundle
react-native bundle --platform windows --entry-file index.js --bundle-output test.bundle
About this issue
- Original URL
- State: closed
- Created 6 years ago
- Reactions: 23
- Comments: 24 (3 by maintainers)
@rubennorte Please, this is still an issue and it’s becoming really frustrating. I had to downgrade to 0.55.4, it worked but there are vulnerabilities that npm suggests npm install react-native @0.56.0 will fix. Going back to that version will return the same “AccessibilityInfo” bug.
What can be done?
this => Unable to resolve module
AccessibilityInfo
is still an issue for 0.56.0, compiling for android on windows platform … what is going wrong ? this is a major issue… i cant believe this is happening for 0.56 after 6 release candidates…A drop grinds the stone. They are working on it. React-native-windows/skype devs are also strugling. I saw one complaining in a related issue. Facebook can’t betray Microsoft 👌
0.56 is broken on windows. Hopefully, this gets fixed soon!
I would like to suggest that the issue detail be updated to reflect the fact that the same issue is happening on Windows 10 when compiling for Android. I spent two days troubleshooting as this happened during my very first react native project setup 😦
downgrading isnt really resolving a issue, the originale issue stated that everything worked prior to 0.56
Same question, I’ll almost give up React-native
Same here. When it can be fixed? I dont know how can be released 56 with so many bugs ;/
We need 0.56 release work without module not found issue on android emulator in windows .
I got the same issue on Windows 10 😦