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

AccessbilityInfo error from react-native 0.56 #20204

Closed
callmejm opened this issue Jul 14, 2018 · 7 comments
Closed

AccessbilityInfo error from react-native 0.56 #20204

callmejm opened this issue Jul 14, 2018 · 7 comments
Labels
Resolution: Locked This issue was locked by the bot.

Comments

@callmejm
Copy link

Environment

React Native Environment Info:
System:
OS: Windows 10
CPU: x64 Intel(R) Core(TM) i7-6700HQ CPU @ 2.60GHz
Memory: 6.59 GB / 11.91 GB
Binaries:
Yarn: yarn install v0.27.5
[1/4] Resolving packages...
success Already up-to-date.
Done in 0.64s. - C:\Users\Jayric Mok\AppData\Roaming\npm\yarn.CMD
npm: 6.1.0 - C:\Program Files\nodejs\npm.CMD
IDEs:
Android Studio: Version 3.1.0.0 AI-173.4720617

Description

I tried to create a new react native project v 0.56, but stuck at this error when metro bundle starting.

Loading dependency graph, done.
error: bundling failed: Error: Unable to resolve module AccessibilityInfo from C:\RN\TESTProject\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 #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-*.
    at ModuleResolver.resolveDependency (C:\RN\TESTProject\node_modules\metro\src\node-haste\DependencyGraph\ModuleResolution.js:167:1306)
    at ResolutionRequest.resolveDependency (C:\RN\TESTProject\node_modules\metro\src\node-haste\DependencyGraph\ResolutionRequest.js:80:16)
    at DependencyGraph.resolveDependency (C:\RN\TESTProject\node_modules\metro\src\node-haste\DependencyGraph.js:237:485)
    at Object.resolve (C:\RN\TESTProject\node_modules\metro\src\lib\transformHelpers.js:116:25)
    at dependencies.map.result (C:\RN\TESTProject\node_modules\metro\src\DeltaBundler\traverseDependencies.js:298:29)
    at Array.map ()
    at resolveDependencies (C:\RN\TESTProject\node_modules\metro\src\DeltaBundler\traverseDependencies.js:294:16)
    at C:\RN\TESTProject\node_modules\metro\src\DeltaBundler\traverseDependencies.js:159:33
    at Generator.next ()
    at step (C:\RN\TESTProject\node_modules\metro\src\DeltaBundler\traverseDependencies.js:239:307)
    BUNDLE [android, dev] ....../index.js ░░░░░░░░░░░░░░░░ 1.1% (2/19), failed.

react-native version

react-native-cli: 2.0.1
react-native: 0.56.0

Package

{
  "name": "TESTProject",
  "version": "0.0.1",
  "private": true,
  "scripts": {
	"start": "node node_modules/react-native/local-cli/cli.js start",
	"test": "jest"
  },
  "dependencies": {
	"react": "16.4.1",
	"react-native": "0.56.0"
  },
  "devDependencies": {
	"babel-jest": "23.4.0",
	"babel-preset-react-native": "5",
	"jest": "23.4.1",
	"react-test-renderer": "16.4.1"
  },
  "jest": {
	"preset": "react-native"
  }
}
@bhram
Copy link

bhram commented Jul 14, 2018

same here

@phuochoit
Copy link

Me too

1 similar comment
@ZLGong
Copy link

ZLGong commented Jul 14, 2018

Me too

@kelset
Copy link
Contributor

kelset commented Jul 14, 2018

Duplicate of #19953

@kelset kelset marked this as a duplicate of #19953 Jul 14, 2018
@kelset kelset closed this as completed Jul 14, 2018
@yangy996
Copy link

me too

@naiduprakash
Copy link

same here would anybody find the solution for it?

@yangy996
Copy link

I found a way. "react-native": "^0.56.0" => "react-native": "^0.55.4" in package.json

@facebook facebook locked as off-topic and limited conversation to collaborators Jul 18, 2018
@react-native-bot react-native-bot added the Resolution: Locked This issue was locked by the bot. label Jul 18, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Resolution: Locked This issue was locked by the bot.
Projects
None yet
Development

No branches or pull requests

8 participants