RN 0.63 Update - Unable to resolve module `../Components/AccessibilityInfo/AccessibilityInfo` #5965

virginiarcruz · 2020-09-11T11:50:51Z

I'm having issues updating the react-native version on RNW project.
Currently, the project has:

"react-native-windows": "0.59.0-legacy.1",
"react-native": "0.59.0",

After the update, RN 0.59 for 0.63 then while building a react-native app, happen an error that says:

error: Error: Unable to resolve module `./Libraries/Components/AccessibilityInfo/AccessibilityInfo` from `node_modules\react-native\index.js`: 

None of these files exist:
  * node_modules\react-native\Libraries\Components\AccessibilityInfo\AccessibilityInfo(.native|.windows.jsx|.native.jsx|.jsx|.windows.js|.native.js|.js|.windows.json|.native.json|.json|.windows.ts|.native.ts|.ts|.windows.tsx|.native.tsx|.tsx)
  * node_modules\react-native\Libraries\Components\AccessibilityInfo\AccessibilityInfo\index(.native|.windows.jsx|.native.jsx|.jsx|.windows.js|.native.js|.js|.windows.json|.native.json|.json|.windows.ts|.native.ts|.ts|.windows.tsx|.native.tsx|.tsx)
    at ModuleResolver.resolveDependency (c:\Projects\myproject\mainDirectory\node_modules\react-native\node_modules\metro\src\node-haste\DependencyGraph\ModuleResolution.js:163:15)
    at ResolutionRequest.resolveDependency (c:\Projects\myproject\mainDirectory\node_modules\react-native\node_modules\metro\src\node-haste\DependencyGraph\ResolutionRequest.js:52:18)
    at DependencyGraph.resolveDependency (c:\Projects\myproject\mainDirectory\node_modules\react-native\node_modules\metro\src\node-haste\DependencyGraph.js:287:16)
    at Object.resolve (c:\Projects\myproject\mainDirectory\node_modules\react-native\node_modules\metro\src\lib\transformHelpers.js:267:42)
    at c:\Projects\myproject\mainDirectory\node_modules\react-native\node_modules\metro\src\DeltaBundler\traverseDependencies.js:434:31
    at Array.map (<anonymous>)
    at resolveDependencies (c:\Projects\myproject\mainDirectory\node_modules\react-native\node_modules\metro\src\DeltaBundler\traverseDependencies.js:431:18)
    at c:\Projects\myproject\mainDirectory\node_modules\react-native\node_modules\metro\src\DeltaBundler\traverseDependencies.js:275:33
    at Generator.next (<anonymous>)
    at asyncGeneratorStep (c:\Projects\myproject\mainDirectory\node_modules\react-native\node_modules\metro\src\DeltaBundler\traverseDependencies.js:87:24)

Is there any solution to my problem or this RNW version (0.59) has any limitation to the RN version (0.63)?

Thanks!

The text was updated successfully, but these errors were encountered:

asklar · 2020-09-12T08:24:17Z

Looks like a dupe of #5604

virginiarcruz · 2020-09-14T11:41:25Z

Seems that a similar issue, but my RNW is 0.59 instead of vnext.
So, mean that on the RNW 0.59 is not possible to have the RN 0.63?

acoates-ms · 2020-09-14T16:18:40Z

#5604 is a different issue. This is a metro config issue, not a runtime issue.

I forget the exact setup required for 0.59, but the fact that metro is loading node_modules\react-native\index.js in the first place indicates a metro config error. It shouldn't be loading any files from react-native, and instead be using files from react-native-windows. For windows we redirect all imports for react-native to react-native-windows. Its fairly complex to get the metro config for 0.59 to do that. It got much simpler in 0.62. (Basically the CLI should do it automatically for you)

chrisglein · 2020-09-14T19:00:44Z

@virginiarcruz Can you provide some more info like your metro config? We've been through a lot between 0.59 and 0.63. Like a lot a lot. So we're glad to see you going through this upgrade but a fair amount has happened. How are you approaching your upgrade? Your best experience is likely going to be creating a new empty app and migrating your app JS/native content over to that.

virginiarcruz · 2020-09-14T19:44:46Z

@chrisglein
Currently, I have a monorepo as a structure bellow

myproject/
| package.json (monorepo config)
/packages
/project
   | package.json (monorepo config)
   | metro.config

And the metro.config has this config


const path = require('path');
const blacklist = require('metro-config/src/defaults/blacklist');

const parentFolderName = path
  .resolve(__dirname, '..')
  .split(path.sep)
  .pop();

const blacklistRE = blacklist([ AllBlackListContants ]);

module.exports = {
  resolver: {
    blacklistRE,
    sourceExts: ['jsx', 'js', 'json', 'ts', 'tsx']
  },
  watchFolders: [path.resolve(__dirname, '../packages'), path.resolve(__dirname, '../node_modules')]
};

chrisglein · 2020-09-17T18:42:30Z

I'm not sure what specifically is going to be wrong with that metro.config. May be fine but it's unclear what's in the blacklist? At first glance it looks like maybe fine? With you being in a monorepo you will need a custom config.

We've seen this error with a stale cache before. Can you try this and let us know if it works or not?
yarn start --reset-cache
(may be needed after an upgrade)

virginiarcruz · 2020-09-18T12:31:23Z

@chrisglein
This is my blacklist:

const blacklistRE = blacklist([
  /package-name[^\\/\\]*[\\/\\]node_modules[\\/\\]react-native[\\/\\].*/,
  /package-name[^\\/\\]*[\\/\\]node_modules[\\/\\]react-native-windows[\\/\\].*/,
  new RegExp(`${parentFolderName}[\\${path.sep}]node_modules[\\${path.sep}]react-native[\\${path.sep}].*`),
  new RegExp(`${parentFolderName}[\\${path.sep}]node_modules[\\${path.sep}]react-native-windows[\\${path.sep}].*`),
  /project\\windows\\.*/,
  /project\\.vscode\\.*/
]);

Even doing the reset on bundle the app still displays the same error. 😔

acoates-ms · 2020-09-18T15:49:38Z

Why are you blacklisting react-native-windows? That would cause it to not be able to load files from react-native-windows.

Can you also check that your version of @react-native-community/cli is >= 4.9?

virginiarcruz · 2020-09-18T19:44:10Z

@acoates-ms
My version of @react-native-community/cli@^1.2.1
👀

acoates-ms · 2020-09-18T20:25:18Z

RN 0.63 needs a newer version of the CLI than that. -- You should have >= 4.9.

virginiarcruz · 2020-09-21T16:48:58Z

@acoates-ms
I updated the react-native-community/cli to ^4.13.0
The app now seems to run but the same error is logged on the bundle.

Btw, will be possible to have a 0.59 RNW version and 0.63 RN?

ugrylmz · 2020-09-25T15:02:41Z

My monorepo project structure is:
myproject/
| package.json (main monorepo config) includes
"workspaces": { "packages": [ "packages/*" ], "nohoist": [ "**/react-native-windows", "**/react-native-windows/**" ] },
/packages
/mobile
| package.json (monorepo config(dirname)) "react-native-windows": "^0.63.0-0","react-native": "0.63.2", "shared": "0.0.1",
| metro.config
| android
| ios
| windows

/shared
| src/setup.js

import setupApp from 'reduxstore/src/setup';
import setupNavigation from '<mynavigationlibrary>-navigation/src/setup';
import AppNavigator from './navigation/AppNavigator';

const Root = setupApp(setupNavigation(AppNavigator));

export default Root;

also includes
/web

when I run npx react-native run-windows


Error: Unable to resolve module `shared/src/setup` from `index.js`: shared/src/setup could not be found within the project.

If you are sure the module exists, try these steps:
 1. Clear watchman watches: watchman watch-del-all
 2. Delete node_modules: rm -rf node_modules and run yarn install
 3. Reset Metro's cache: yarn start --reset-cache
 4. Remove the cache: rm -rf /tmp/metro-*
    at ModuleResolver.resolveDependency (C:\repos\.........\.................\packages\mobile\node_modules\metro\src\node-haste\DependencyGraph\ModuleResolution.js:186:15)
    at ResolutionRequest.resolveDependency (C:\repos\.........\.................\packages\mobile\node_modules\metro\src\node-haste\DependencyGraph\ResolutionRequest.js:52:18)
    at DependencyGraph.resolveDependency (C:\repos\.........\.................\packages\mobile\node_modules\metro\src\node-haste\DependencyGraph.js:287:16)
    at Object.resolve (C:\repos\.........\.................\packages\mobile\node_modules\metro\src\lib\transformHelpers.js:267:42)
    at C:\repos\.........\.................\packages\mobile\node_modules\metro\src\DeltaBundler\traverseDependencies.js:434:31
    at Array.map (<anonymous>)
    at resolveDependencies (C:\repos\.........\.................\\packages\mobile\node_modules\metro\src\DeltaBundler\traverseDependencies.js:431:18)
    at C:\repos\BEINCONNECTUI\.........\.................\mobile\node_modules\metro\src\DeltaBundler\traverseDependencies.js:275:33
    at Generator.next (<anonymous>)
    at asyncGeneratorStep (C:\repos\.........\.................\packages\mobile\node_modules\metro\src\DeltaBundler\traverseDependencies.js:87:24)

I am sure the module exists and in mobile other platforms works without any errors.
I tried all of the steps and the result was same.


npx react-native --version: 4.13.0
npx react-native run-windows --info:
 System:
    OS: Windows 10 10.0.17763
    CPU: (12) x64 Intel(R) Core(TM) i7-8700 CPU @ 3.20GHz
    Memory: 2.07 GB / 15.87 GB
  Binaries:
    Node: 12.2.0 - C:\Program Files\nodejs\node.EXE
    Yarn: 1.22.4 - C:\Program Files (x86)\Yarn\bin\yarn.CMD
    npm: 6.9.0 - C:\Program Files\nodejs\npm.CMD
  npmPackages:
    react: 16.13.1 => 16.13.1
    react-native: 0.63.2 => 0.63.2
    react-native-windows: ^0.63.0-0 => 0.63.3
  Installed UWP SDKs:
    10.0.14393.0
    10.0.17763.0
    10.0.18362.0
react-native-cli: 2.0.1
react-native: 0.63.2
npm ls rnpm-plugin-windows: [email protected] C:\repos\....\......UI\packages\mobile
yarn --version : 1.22.4
node -v : v12.2.0
npm -v: 6.9.0

acoates-ms · 2020-09-25T16:11:29Z

@ugrylmz, that import looks like maybe you meant it to be a relative import? './shared/src/setup' instead of 'shared/src/setup'?

ugrylmz · 2020-09-28T06:09:50Z

@acoates-ms , I tried but the result is same.

acoates-ms · 2020-09-28T16:44:17Z

Can you see if any of the information here helps:
https://microsoft.github.io/react-native-windows/docs/next/metro-config-out-tree-platforms

ugrylmz · 2020-10-01T12:50:16Z

error: Error: Unable to resolve module "@babel/runtime/helpers/interopRequireDefault" from "..\shared\src\setup.js": @babel/runtime/helpers/interopRequireDefault could not be found within the project.
I added to project

"@babel/core": "^7.5.4",
"@babel/runtime": "^7.5.4",

I tried

    Clear watchman watches: watchman watch-del-all
    Delete node_modules: rm -rf node_modules and run yarn install
    Reset Metro's cache: yarn start --reset-cache
    Remove the cache: rm -rf /tmp/metro-*

Can you see if any of the information here helps:
https://microsoft.github.io/react-native-windows/docs/next/metro-config-out-tree-platforms

According to the link that you shared, i reconfigured the metro.config file as below:

/**
 * Metro configuration for React Native
 * https://github.com/facebook/react-native
 *
 * @format
 */
const path = require('path');
const blacklist = require('metro-config/src/defaults/blacklist');
const extraNodeModules = {
  'shared': path.resolve(__dirname + '/../shared'),
  'react-native-windows': path.resolve(__dirname + '/windows'),
};
const watchFolders = [
  path.resolve(__dirname + '/../shared'),
  path.resolve(__dirname + '/windows')
];

module.exports = {
  resolver: {
    blacklistRE: blacklist([
      // This stops "react-native run-windows" from causing the metro server to crash if its already running
      new RegExp(
        `${path.resolve(__dirname, 'windows').replace(/[/\\]/g, '/')}.*`,
      ),
      // This prevents "react-native run-windows" from hitting: EBUSY: resource busy or locked, open msbuild.ProjectImports.zip
      /.*\.ProjectImports\.zip/,
    ]),
  },
  transformer: {
    getTransformOptions: async () => ({
      transform: {
        experimentalImportSupport: false,
        inlineRequires: false,
      },
    }),
  },
  resolver: {
    extraNodeModules
  },
  watchFolders,
};

acoates-ms · 2020-10-01T15:01:38Z

I'm guessing you are using yarn workspaces, and the packages in question have been hoisted up to a location that isn't being included in the watchFolders?

Can you provide information about where the @babel/runtime pacakge was installed to? Whats the location on disk of that packaage in node_modules, compared to these windows and shared folders.

asklar · 2020-10-01T15:41:33Z

meta-point, is there something we can add to an info command to collect information about their metro env if they're having metro issues? e.g. create a github issue template for "I'm having metro problems" where it collects their metro.config.js, general project structure, etc. but automatic?

ugrylmz · 2020-10-06T11:30:50Z

I'm guessing you are using yarn workspaces, and the packages in question have been hoisted up to a location that isn't being included in the watchFolders?

Can you provide information about where the @babel/runtime pacakge was installed to? Whats the location on disk of that packaage in node_modules, compared to these windows and shared folders.

Yes, I am using yarn-worksapaces,
monorepo-project/
/node_modules/@babel/runtime/helpers
| package.json (main monorepo package.json) includes

 "workspaces": {
    "packages": [
      "packages/*"
    ],
    "nohoist": [
       "**/react-native-windows",
        "**/react-native-windows/**"
    ]
  },
"devDependencies": {
    "babel-eslint": "^10.1.0",
    "@babel/runtime": "^7.0.0-beta.55",
    "@babel/core": "^7.0.0-beta.55",
    "better-docs": "2.3.0",
.
.
.
}

/packages/mobile/node_modules/@babel/runtime/helpers

| package.json

 "dependencies": {
    "@react-navigation/native": "5.6.1",
    "@react-navigation/stack": "5.6.2",
    "react": "16.12.0",
    "react-native": "0.63.2",
    "react-native-gesture-handler": "1.7.0",
    "react-native-platform-touchable": "^1.1.1",
    "reduxstore": "0.0.1",
    "shared": "0.0.1",
    "react-native-windows": "^0.63.0-0"
  },
  "devDependencies": {
    "@react-native-community/eslint-config": "0.0.7",
    "@react-native-community/netinfo": "5.9.6",
    "@testing-library/jest-native": "3.0.3",
    "@testing-library/react-native": "5.0.1",
    "babel-jest": "25.1.0",
    "@babel/runtime": "^7.0.0-beta.55",
    "@babel/core": "^7.0.0-beta.55",
    "jest": "25.1.0",
    "shared": "0.0.1",
    "metro-react-native-babel-preset": "^0.59.0",
    "react-native-safe-area-context": "^3.1.4",
    "react-test-renderer": "16.12.0"
  }

| babel.config.js

module.exports = {
  presets: ['module:metro-react-native-babel-preset'],
};

| metro.config.js

/**
 * Metro configuration for React Native
 * https://github.com/facebook/react-native
 *
 * @format
 */
const path = require('path');
const blacklist = require('metro-config/src/defaults/blacklist');
const extraNodeModules = {
  'shared': path.resolve(__dirname + '/../shared'),
  'react-native-windows': path.resolve(__dirname + '/windows'),
  'shared-node_modules': path.resolve(__dirname, '/monorepo-project/packages/shared/node_modules'),
  'react-native':  path.resolve(`${__dirname}/node_modules/react-native`)
};
console.log('__dirname ------------------------------',__dirname); // C:\monorepo-project\packages\mobile
console.log('------------------------------',path.resolve(__dirname, '/monorepo-project/packages/shared/node_modules'));
const watchFolders = [
  path.resolve(__dirname + '/../shared'),
  path.resolve(__dirname + '/windows'),
  path.resolve(__dirname, '/monorepo-project/packages/shared/node_modules'),
  path.resolve(`${__dirname}/node_modules/react-native`)
];

module.exports = {
  resolver: {
    blacklistRE: blacklist([
      // This stops "react-native run-windows" from causing the metro server to crash if its already running
      new RegExp(
        `${path.resolve(__dirname, 'windows').replace(/[/\\]/g, '/')}.*`,
      ),
      // This prevents "react-native run-windows" from hitting: EBUSY: resource busy or locked, open msbuild.ProjectImports.zip
      /.*\.ProjectImports\.zip/,
    ]),
  },
  transformer: {
    getTransformOptions: async () => ({
      transform: {
        experimentalImportSupport: false,
        inlineRequires: false,
      },
    }),
  },
  resolver: {
    extraNodeModules
  },
  watchFolders,
};

| react-native.config.js

module.exports = {
  assets: ['../shared/assets/fonts/']
};

ghost · 2020-10-13T14:00:07Z

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 7 days. It will be closed if no further activity occurs within 14 days of this comment.

ugrylmz · 2020-10-19T06:32:01Z

Is there any solution to my problem?

ghost · 2020-10-26T08:00:08Z

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 7 days. It will be closed if no further activity occurs within 14 days of this comment.

acoates-ms · 2020-10-26T15:53:32Z

It looks like to satisfy at least some of your dependencies @babel/runtime was hoisted to the root of the repo. So you'd need to include monorepo-project/node_modules in your watch folders.

ghost · 2020-11-02T17:00:06Z

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 7 days. It will be closed if no further activity occurs within 14 days of this comment.

lh9403 · 2021-01-29T10:11:04Z

Has anyone solved the same problem?

version：
"react-native": "^0.63.4",
"react-native-macos": "^0.63.0-0",

Unable to resolve module ./Libraries/Components/AccessibilityInfo/AccessibilityInfo from node_modules/react-native/index.js:

None of these files exist:

node_modules/react-native/Libraries/Components/AccessibilityInfo/AccessibilityInfo(.native|.macos.js|.native.js|.js|.macos.json|.native.json|.json|.macos.ts|.native.ts|.ts|.macos.tsx|.native.tsx|.tsx)
node_modules/react-native/Libraries/Components/AccessibilityInfo/AccessibilityInfo/index(.native|.macos.js|.native.js|.js|.macos.json|.native.json|.json|.macos.ts|.native.ts|.ts|.macos.tsx|.native.tsx|.tsx)

RCTFatal
__28-[RCTCxxBridge handleError:]_block_invoke
_dispatch_call_block_and_release
_dispatch_client_callout
_dispatch_main_queue_callback_4CF
CFRUNLOOP_IS_SERVICING_THE_MAIN_DISPATCH_QUEUE
__CFRunLoopRun
CFRunLoopRunSpecific
RunCurrentEventLoopInMode
ReceiveNextEventCommon
_BlockUntilNextEventMatchingListInModeWithFilter
_DPSNextEvent
-[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:]
-[NSApplication run]
NSApplicationMain
main
start
0x0

chrisglein · 2021-02-08T18:36:12Z

@lh9403 There were a lot of suggestions on this thread for what could be wrong. Have you tried the metro troubleshooting tips and other suggestions?

DanielRiera · 2021-02-24T17:37:06Z

Run npm install and working :)

avaneeshtripathi · 2023-04-19T20:07:47Z

@lh9403 Were you able to solve this?

react-native: 0.64.2

jljonnard · 2023-09-01T16:00:22Z

I experienced the exact same issue on Android in RN 0.72.4 and deleting the cxx folder in Android/App has worked for me.

virginiarcruz added the question label Sep 11, 2020

ghost added the Needs: Triage 🔍 New issue that needs to be reviewed by the issue management team (label applied by bot) label Sep 11, 2020

chrisglein mentioned this issue Sep 14, 2020

Create/link app guide for RNW version update best practices microsoft/react-native-windows-samples#258

Closed

chrisglein added Needs: Author Feedback The issue/PR needs activity from its author (label drives bot activity) and removed Needs: Triage 🔍 New issue that needs to be reviewed by the issue management team (label applied by bot) labels Sep 14, 2020

ghost added Needs: Attention 👋 An issue that had been tagged "Needs: Author Feedback" has received activity (label applied by bot) and removed Needs: Author Feedback The issue/PR needs activity from its author (label drives bot activity) labels Sep 18, 2020

acoates-ms added Needs: Author Feedback The issue/PR needs activity from its author (label drives bot activity) and removed Needs: Attention 👋 An issue that had been tagged "Needs: Author Feedback" has received activity (label applied by bot) labels Sep 18, 2020

ghost added Needs: Attention 👋 An issue that had been tagged "Needs: Author Feedback" has received activity (label applied by bot) and removed Needs: Author Feedback The issue/PR needs activity from its author (label drives bot activity) labels Sep 18, 2020

acoates-ms added Needs: Author Feedback The issue/PR needs activity from its author (label drives bot activity) and removed Needs: Attention 👋 An issue that had been tagged "Needs: Author Feedback" has received activity (label applied by bot) labels Sep 18, 2020

ghost added the no-recent-activity Issue/PR has gone stale and may be closed (label applied by bot) label Oct 13, 2020

ghost removed the no-recent-activity Issue/PR has gone stale and may be closed (label applied by bot) label Oct 19, 2020

ghost added the no-recent-activity Issue/PR has gone stale and may be closed (label applied by bot) label Oct 26, 2020

ghost removed the no-recent-activity Issue/PR has gone stale and may be closed (label applied by bot) label Oct 26, 2020

ghost added the no-recent-activity Issue/PR has gone stale and may be closed (label applied by bot) label Nov 2, 2020

ghost closed this as completed Nov 16, 2020

ghost added Needs: Attention 👋 An issue that had been tagged "Needs: Author Feedback" has received activity (label applied by bot) and removed no-recent-activity Issue/PR has gone stale and may be closed (label applied by bot) labels Jan 29, 2021

chrisglein removed the Needs: Attention 👋 An issue that had been tagged "Needs: Author Feedback" has received activity (label applied by bot) label Feb 8, 2021

ghost added the Needs: Attention 👋 An issue that had been tagged "Needs: Author Feedback" has received activity (label applied by bot) label Feb 24, 2021

chrisglein removed the Needs: Attention 👋 An issue that had been tagged "Needs: Author Feedback" has received activity (label applied by bot) label Feb 25, 2021

howlettt mentioned this issue Apr 18, 2021

Documentation on using metro bundler necolas/react-native-web#1257

Closed

This issue was closed.

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

RN 0.63 Update - Unable to resolve module `../Components/AccessibilityInfo/AccessibilityInfo` #5965

RN 0.63 Update - Unable to resolve module `../Components/AccessibilityInfo/AccessibilityInfo` #5965

virginiarcruz commented Sep 11, 2020 •

edited

Loading

asklar commented Sep 12, 2020

virginiarcruz commented Sep 14, 2020

acoates-ms commented Sep 14, 2020

chrisglein commented Sep 14, 2020

virginiarcruz commented Sep 14, 2020 •

edited

Loading

chrisglein commented Sep 17, 2020

virginiarcruz commented Sep 18, 2020

acoates-ms commented Sep 18, 2020

virginiarcruz commented Sep 18, 2020 •

edited

Loading

acoates-ms commented Sep 18, 2020

virginiarcruz commented Sep 21, 2020

ugrylmz commented Sep 25, 2020 •

edited

Loading

acoates-ms commented Sep 25, 2020

ugrylmz commented Sep 28, 2020

acoates-ms commented Sep 28, 2020

ugrylmz commented Oct 1, 2020

acoates-ms commented Oct 1, 2020

asklar commented Oct 1, 2020

ugrylmz commented Oct 6, 2020 •

edited

Loading

ghost commented Oct 13, 2020

ugrylmz commented Oct 19, 2020

ghost commented Oct 26, 2020

acoates-ms commented Oct 26, 2020

ghost commented Nov 2, 2020

lh9403 commented Jan 29, 2021

chrisglein commented Feb 8, 2021

DanielRiera commented Feb 24, 2021

avaneeshtripathi commented Apr 19, 2023

jljonnard commented Sep 1, 2023

RN 0.63 Update - Unable to resolve module ../Components/AccessibilityInfo/AccessibilityInfo #5965

RN 0.63 Update - Unable to resolve module ../Components/AccessibilityInfo/AccessibilityInfo #5965

Comments

virginiarcruz commented Sep 11, 2020 • edited Loading

asklar commented Sep 12, 2020

virginiarcruz commented Sep 14, 2020

acoates-ms commented Sep 14, 2020

chrisglein commented Sep 14, 2020

virginiarcruz commented Sep 14, 2020 • edited Loading

chrisglein commented Sep 17, 2020

virginiarcruz commented Sep 18, 2020

acoates-ms commented Sep 18, 2020

virginiarcruz commented Sep 18, 2020 • edited Loading

acoates-ms commented Sep 18, 2020

virginiarcruz commented Sep 21, 2020

ugrylmz commented Sep 25, 2020 • edited Loading

acoates-ms commented Sep 25, 2020

ugrylmz commented Sep 28, 2020

acoates-ms commented Sep 28, 2020

ugrylmz commented Oct 1, 2020

acoates-ms commented Oct 1, 2020

asklar commented Oct 1, 2020

ugrylmz commented Oct 6, 2020 • edited Loading

ghost commented Oct 13, 2020

ugrylmz commented Oct 19, 2020

ghost commented Oct 26, 2020

acoates-ms commented Oct 26, 2020

ghost commented Nov 2, 2020

lh9403 commented Jan 29, 2021

chrisglein commented Feb 8, 2021

DanielRiera commented Feb 24, 2021

avaneeshtripathi commented Apr 19, 2023

jljonnard commented Sep 1, 2023

RN 0.63 Update - Unable to resolve module `../Components/AccessibilityInfo/AccessibilityInfo` #5965

RN 0.63 Update - Unable to resolve module `../Components/AccessibilityInfo/AccessibilityInfo` #5965

virginiarcruz commented Sep 11, 2020 •

edited

Loading

virginiarcruz commented Sep 14, 2020 •

edited

Loading

virginiarcruz commented Sep 18, 2020 •

edited

Loading

ugrylmz commented Sep 25, 2020 •

edited

Loading

ugrylmz commented Oct 6, 2020 •

edited

Loading