RN 0.59.10 Unable to resolve module `AccessibilityInfo` .... ..... Module `AccessibilityInfo` does not exist in the Haste module map
See original GitHub issueBUNDLE [dev] ./index.js ▓▓▓▓▓░░░░░░░░░░░ 36.0% (9/15)::1 - - [02/Apr/2020:15:50:07 +0000] “GET /index.bundle HTTP/1.1” 500 - “-” “Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/80.0.3987.149 Safari/537.36”
error: bundling failed: Error: Unable to resolve module AccessibilityInfo
from /Users/coolqi/GitHubCode/rnText/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:
- Clear watchman watches:
watchman watch-del-all
. - Delete the
node_modules
folder:rm -rf node_modules && npm install
. - Reset Metro Bundler cache:
rm -rf /tmp/metro-bundler-cache-*
ornpm start -- --reset-cache
. - Remove haste cache:
rm -rf /tmp/haste-map-react-native-packager-*
. at ModuleResolver.resolveDependency (/Users/coolqi/GitHubCode/rnText/node_modules/metro/src/node-haste/DependencyGraph/ModuleResolution.js:183:15) at ResolutionRequest.resolveDependency (/Users/coolqi/GitHubCode/rnText/node_modules/metro/src/node-haste/DependencyGraph/ResolutionRequest.js:52:18) at DependencyGraph.resolveDependency (/Users/coolqi/GitHubCode/rnText/node_modules/metro/src/node-haste/DependencyGraph.js:283:16) at Object.resolve (/Users/coolqi/GitHubCode/rnText/node_modules/metro/src/lib/transformHelpers.js:261:42) at /Users/coolqi/GitHubCode/rnText/node_modules/metro/src/DeltaBundler/traverseDependencies.js:399:31 at Array.map (<anonymous>) at resolveDependencies (/Users/coolqi/GitHubCode/rnText/node_modules/metro/src/DeltaBundler/traverseDependencies.js:396:18) at /Users/coolqi/GitHubCode/rnText/node_modules/metro/src/DeltaBundler/traverseDependencies.js:269:33 at Generator.next (<anonymous>) at asyncGeneratorStep (/Users/coolqi/GitHubCode/rnText/node_modules/metro/src/DeltaBundler/traverseDependencies.js:87:24) BUNDLE [dev] ./index.js ▓▓▓▓▓░░░░░░░░░░░ 36.0% (9/15), failed.
Issue Analytics
- State:
- Created 3 years ago
- Comments:10 (2 by maintainers)
Top Results From Across the Web
Unable to resolve module 'AccessibilityInfo', when trying ...
It seems like a bug in 0.56 related to dependencies. The "solution" is to find the correct combination of dependencies' versions. We found...
Read more >Solved: Unable to resolve module AccessibilityInfo
Unable to resolve module `AccessibilityInfo`: Module does not exist in the module map. So, what is the cause of this error and how...
Read more >Unable to resolve module `AccessibilityInfo`
I am trying to create a new React-Native project from WebStorm IDE. After I run 'npm install' and click on 'Run' button in...
Read more >at moduleresolver.resolvedependency
Error: Unable to resolve module `buffer` React Native ... facebook/react-nativeModule `AccessibilityInfo` does not exist in the Haste module map#28479.
Read more >AccessibilityInfo
Sometimes it's useful to know whether or not the device has a screen reader that is currently active. The AccessibilityInfo API is designed ......
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I have this issue with
0.63.4
, and I’ve been reviewing reports of this error all the way back to0.44.1
. Unfortunately, the consensus seems to always be that each version is simply broken and the solution is to upgrade. The issues are usually closed as resolve, stale or spam before any other solution or cause is explored. Unless the maintainers are repeatedly breaking the project in the same way over the course of years, I think it’s safe to say that it’s not really a problem with countless versions, and that upgrading is simply having the side effect of fixing some other local problem.Any thoughts or trouble shooting ideas for this besides upgrading?
react-native info
in a console.