Invariant Violation: Module AppRegistry is not a registered callabel module (calling runApplication)

Question

Invariant Violation: Module AppRegistry is not a registered callabel module (calling runApplication)

Hugo-Meiring opened this issue 6 years ago · 158 comments

Currently on React Native 0.61.0-rc.3, updating to 0.61.1 causes this issue.

React Native version:

info Fetching system and libraries information...
System:
    OS: macOS 10.14.6
    CPU: (12) x64 Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz
    Memory: 871.19 MB / 16.00 GB
    Shell: 5.3 - /bin/zsh
  Binaries:
    Node: 12.10.0 - /usr/local/bin/node
    Yarn: 1.17.3 - /usr/local/bin/yarn
    npm: 6.11.3 - /usr/local/bin/npm
    Watchman: 4.9.0 - /usr/local/bin/watchman
  SDKs:
    iOS SDK:
      Platforms: iOS 13.0, DriverKit 19.0, macOS 10.15, tvOS 13.0, watchOS 6.0
    Android SDK:
      API Levels: 28, 29
      Build Tools: 28.0.3, 29.0.2
      System Images: android-29 | Google APIs Intel x86 Atom
  IDEs:
    Android Studio: 3.5 AI-191.8026.42.35.5791312
    Xcode: 11.0/11A420a - /usr/bin/xcodebuild
  npmPackages:
    react: 16.9.0 => 16.9.0 
    react-native: 0.61.1 => 0.61.1 
  npmGlobalPackages:
    react-native-cli: 2.0.1

Steps To Reproduce

Update the package.json values to use latest 0.61.1 (and other latest values pulled for a react-native init)
Run the project (yarn && cd ios && pod install && cd .. && yarn start + yarn ios)

Describe what you expected to happen:
The app should be running like on 0.61.0-rc.3. What major changes where made between the release candidate and 0.61.0 (also your website still show 0.60.0 as the latest version). Here is the source code changes between the two:
https://react-native-community.github.io/upgrade-helper/?from=0.61.0-rc.3&to=0.61.1

Snack, code example, screenshot, or link to a repository:

Can't be provided, production and private react-native init application.

Answer 1 · 2019-10-02T12:04:17.000Z

Unfortunately, this error does not give any feedback on what exactly is wrong. You need to dig deeper.

Answer 2 · 2019-10-02T12:23:44.000Z

Here are logs from Xcode:

2019-10-02 14:19:16.303 [error][tid:com.facebook.react.JavaScript] Invariant Violation: Module AppRegistry is not a registered callable module (calling runApplication)
2019-10-02 14:19:16.305 [fatal][tid:com.facebook.react.ExceptionsManagerQueue] Unhandled JS Exception: Invariant Violation: Module AppRegistry is not a registered callable module (calling runApplication)
2019-10-02 14:19:16.311 [error][tid:com.facebook.react.JavaScript] Invariant Violation: No callback found with cbID 2 and callID 1 for module <unknown>. Args: '[{"app_state":"active"}]'
2019-10-02 14:19:16.313 [error][tid:com.facebook.react.JavaScript] Invariant Violation: No callback found with cbID 18 and callID 9 for module <unknown>. Args: '[{"app_state":"active"}]'
2019-10-02 14:19:16.314 [error][tid:com.facebook.react.JavaScript] Invariant Violation: No callback found with cbID 40 and callID 20 for module <unknown>. Args: '[{"app_state":"active"}]'
2019-10-02 14:19:16.317 [fatal][tid:com.facebook.react.ExceptionsManagerQueue] Unhandled JS Exception: Invariant Violation: No callback found with cbID 2 and callID 1 for module <unknown>. Args: '[{"app_state":"active"}]'
2019-10-02 14:19:16.318 [error][tid:com.facebook.react.JavaScript] Invariant Violation: No callback found with cbID 73 and callID 36 for module <unknown>. Args: '[0]'
2019-10-02 14:19:16.319 [error][tid:com.facebook.react.JavaScript] Invariant Violation: No callback found with cbID 99 and callID 49 for module <unknown>. Args: '[1]'
2019-10-02 14:19:16.320 [fatal][tid:com.facebook.react.ExceptionsManagerQueue] Unhandled JS Exception: Invariant Violation: No callback found with cbID 18 and callID 9 for module <unknown>. Args: '[{"app_state":"active"}]'
2019-10-02 14:19:16.322 [error][tid:com.facebook.react.JavaScript] Invariant Violation: No callback found with cbID 123 and callID 61 for module <unknown>. Args: '[2]'
2019-10-02 14:19:16.323 [error][tid:com.facebook.react.JavaScript] Invariant Violation: No callback found with cbID 139 and callID 69 for module <unknown>. Args: '[3]'
2019-10-02 14:19:16.323 [error][tid:com.facebook.react.JavaScript] Invariant Violation: No callback found with cbID 155 and callID 77 for module <unknown>. Args: '[4]'
2019-10-02 14:19:16.324 [fatal][tid:com.facebook.react.ExceptionsManagerQueue] Unhandled JS Exception: Invariant Violation: No callback found with cbID 40 and callID 20 for module <unknown>. Args: '[{"app_state":"active"}]'
2019-10-02 14:19:16.327 [fatal][tid:com.facebook.react.ExceptionsManagerQueue] Unhandled JS Exception: Invariant Violation: No callback found with cbID 73 and callID 36 for module <unknown>. Args: '[0]'
2019-10-02 14:19:16.329 [fatal][tid:com.facebook.react.ExceptionsManagerQueue] Unhandled JS Exception: Invariant Violation: No callback found with cbID 99 and callID 49 for module <unknown>. Args: '[1]'
2019-10-02 14:19:16.330278+0200 libertychat[59943:2042874] [] nw_proxy_resolver_create_parsed_array [C8 proxy pac] Evaluation error: NSURLErrorDomain: -1003
2019-10-02 14:19:16.330 [error][tid:com.facebook.react.JavaScript] Invariant Violation: No callback found with cbID 171 and callID 85 for module <unknown>. Args: '[5]'
2019-10-02 14:19:16.331 [error][tid:com.facebook.react.JavaScript] Invariant Violation: No callback found with cbID 187 and callID 93 for module <unknown>. Args: '[6]'
2019-10-02 14:19:16.367066+0200 libertychat[59943:2042874] [] nw_proxy_resolver_create_parsed_array [C10 proxy pac] Evaluation error: NSURLErrorDomain: -1003
2019-10-02 14:19:16.368 [error][tid:com.facebook.react.JavaScript] Invariant Violation: No callback found with cbID 203 and callID 101 for module <unknown>. Args: '[7]'
2019-10-02 14:19:16.369 [error][tid:com.facebook.react.JavaScript] Invariant Violation: No callback found with cbID 219 and callID 109 for module <unknown>. Args: '[8]'
2019-10-02 14:19:16.369 [error][tid:com.facebook.react.JavaScript] Invariant Violation: No callback found with cbID 239 and callID 119 for module <unknown>. Args: '[9]'
2019-10-02 14:19:16.369809+0200 libertychat[59943:2042874] [] nw_proxy_resolver_create_parsed_array [C11 proxy pac] Evaluation error: NSURLErrorDomain: -1003
2019-10-02 14:19:16.376 [fatal][tid:com.facebook.react.ExceptionsManagerQueue] Unhandled JS Exception: Invariant Violation: No callback found with cbID 123 and callID 61 for module <unknown>. Args: '[2]'
2019-10-02 14:19:16.381 [fatal][tid:com.facebook.react.ExceptionsManagerQueue] Unhandled JS Exception: Invariant Violation: No callback found with cbID 139 and callID 69 for module <unknown>. Args: '[3]'
2019-10-02 14:19:16.385 [fatal][tid:com.facebook.react.ExceptionsManagerQueue] Unhandled JS Exception: Invariant Violation: No callback found with cbID 155 and callID 77 for module <unknown>. Args: '[4]'
2019-10-02 14:19:16.390 [fatal][tid:com.facebook.react.ExceptionsManagerQueue] Unhandled JS Exception: Invariant Violation: No callback found with cbID 171 and callID 85 for module <unknown>. Args: '[5]'
2019-10-02 14:19:16.393 [fatal][tid:com.facebook.react.ExceptionsManagerQueue] Unhandled JS Exception: Invariant Violation: No callback found with cbID 187 and callID 93 for module <unknown>. Args: '[6]'
2019-10-02 14:19:16.393457+0200 libertychat[59943:2042874] [] nw_proxy_resolver_create_parsed_array [C12 proxy pac] Evaluation error: NSURLErrorDomain: -1003
2019-10-02 14:19:16.395 [error][tid:com.facebook.react.JavaScript] Invariant Violation: No callback found with cbID 255 and callID 127 for module <unknown>. Args: '[10]'
2019-10-02 14:19:16.396 [fatal][tid:com.facebook.react.ExceptionsManagerQueue] Unhandled JS Exception: Invariant Violation: No callback found with cbID 203 and callID 101 for module <unknown>. Args: '[7]'
2019-10-02 14:19:16.397 [error][tid:com.facebook.react.JavaScript] Invariant Violation: No callback found with cbID 271 and callID 135 for module <unknown>. Args: '[11]'
2019-10-02 14:19:16.398 [error][tid:com.facebook.react.JavaScript] Invariant Violation: No callback found with cbID 287 and callID 143 for module <unknown>. Args: '[12]'
2019-10-02 14:19:16.399 [error][tid:com.facebook.react.JavaScript] Invariant Violation: No callback found with cbID 303 and callID 151 for module <unknown>. Args: '[13]'
2019-10-02 14:19:16.399 [fatal][tid:com.facebook.react.ExceptionsManagerQueue] Unhandled JS Exception: Invariant Violation: No callback found with cbID 219 and callID 109 for module <unknown>. Args: '[8]'
2019-10-02 14:19:16.403 [fatal][tid:com.facebook.react.ExceptionsManagerQueue] Unhandled JS Exception: Invariant Violation: No callback found with cbID 239 and callID 119 for module <unknown>. Args: '[9]'
2019-10-02 14:19:16.446 [fatal][tid:com.facebook.react.ExceptionsManagerQueue] Unhandled JS Exception: Invariant Violation: No callback found with cbID 255 and callID 127 for module <unknown>. Args: '[10]'```

Answer 3 · 2019-10-02T12:27:37.000Z

Here is are whats if your re-run the app:

Answer 4 · 2019-10-02T12:27:37.000Z

Did you try to enable the Debug option?

Answer 5 · 2019-10-02T12:36:05.000Z

Hugo-Meiring commented 6 years ago

Answer 6 · 2019-10-02T13:17:38.000Z

Getting this same issue but only on Android. Very weird :(

Answer 7 · 2019-10-02T13:37:51.000Z

Did you try to enable the Debug option?

Yes, I also tried toggling Fast Refresh off.

Answer 8 · 2019-10-02T13:57:20.000Z

Fixed the issue on my end by double checking that i modified all the files correctly during my RN upgrade, then running watchman watch-del-all, and react-native start --reset-cache. Then on android, build -> clean. then it worked! sigh

Answer 9 · 2019-10-03T08:57:13.000Z

Unfortunately, it doesn't work our project (iOS) @m4rcoperuano. Glad it worked for you

Answer 10 · 2019-10-03T09:09:15.000Z

It's hard to suggest anything without any more details, I would say that you can try commenting out some parts of your code and try until you find something.

Answer 11 · 2019-10-03T09:48:08.000Z

Fixed the issue on my end by double checking that i modified all the files correctly during my RN upgrade, then running watchman watch-del-all, and react-native start --reset-cache. Then on android, build -> clean. then it worked! sigh

yeah me too,
react-native start --reset-cache
worked on my case

Answer 12 · 2019-10-03T10:53:30.000Z

It's hard to suggest anything without any more details, I would say that you can try commenting out some parts of your code and try until you find something.

Ok will do. This will take a bit of time. We essentially have 2 apps that are linked so changes have to be done for 4 environments (2x iOS and 2x Android). Will report back if I find a solution to this.

Answer 13 · 2019-10-07T19:54:16.000Z

@Hugo-Meiring Probably you use modules that were removed from react-native.
For example ViewPagerAndroid

Answer 14 · 2019-10-08T12:49:44.000Z

So, unfortunately, I just can't get this working. If I get iOS working, Android breaks. If android is working, iOS breaks. This is just one of the issues that I ping pong between depending on the platform.

I can't spend more time on this as this is cutting into the release schedule. Will go with a temporary fix of splitting iOS and Android between different react versions and making adjustments to the CI/CD pipeline. A very nasty solution but it might be for the better. We can possibly move all our shared code to a separate repo while we analyze our options.

Answer 15 · 2019-10-09T21:22:25.000Z

@Hugo-Meiring I'm facing a similar issue on a monorepo (using lerna and yarn workspaces).
Is this your case too?

I found that everything works ok when I start the app without using anything from an external package. Even the fast refresh works correctly if I comment the LOC related to external packages, start the app and finally un-comment those lines.

Answer 16 · 2019-10-10T02:54:14.000Z

Also ran into this (setup below). Took a bit of @m4rcoperuano 's solution and just stopped my simulator and bundler, then removed everything in watchman via watchman watch-del-all. Restarted the simulator via react-native run-ios and everything works fine.

Setup

react-native-cli: 2.0.1
react-native: 0.61.2
mac OSmojave 10.14.6

Answer 17 · 2019-10-15T16:57:30.000Z

This resolved it for me:

$ cd ios && rm -rf Pods && pod cache clean --all && pod install && cd ..

I forgot that I had done a "yarn add ..." on a few NPM modules and forgot to reinstall the pods.

Answer 18 · 2019-10-20T04:08:10.000Z

I have fixed this error, can confirm it's because one of your libraries isn't linked correctly. Fastest way to fix this is starting from index.js to app.js commenting out imports. Once you've commented out enough libraries the app should work then you will know which library was not linked correctly. Some libraries that say they have auto-linking actually don't..... It's very tedious but this works and my app is now fully functioning!

Answer 19 · 2019-11-12T15:05:37.000Z

Why does it have to be so difficult to find out WHICH Native Module cannot be null?

Answer 20 · 2019-11-13T11:24:49.000Z

Hi! I have the same issue, both on android and iOS. I just remove node_modules and install again, it helps me) no other cleans or rebuilds has no effect(

Answer 21 · 2019-11-13T12:58:44.000Z

This is just a vague error to tell you there's something wrong with one of your imports. It can have different causes and has different solutions for each cause. In my case, this was happening because of a circular dependency.

Answer 22 · 2019-12-17T07:09:53.000Z

Also ran into this (setup below). Took a bit of @m4rcoperuano 's solution and just stopped my simulator and bundler, then removed everything in watchman via watchman watch-del-all. Restarted the simulator via react-native run-ios and everything works fine.

Setup
react-native-cli: 2.0.1
react-native: 0.61.2
mac OSmojave 10.14.6

https://github.com/react-native-community/cli#compatibility denotes that react-native 0.61.X needs react-native-cli: 3.0.0

Answer 23 · 2020-01-10T00:41:26.000Z

This solved it for me, using a managed Expo project:

expo start --ios -c

Answer 24 · 2020-01-14T20:14:49.000Z

Another possible reason for this is that there are multiple versions of react-native in node_modules

Answer 25 · 2020-01-14T20:18:20.000Z

Try searching for registerCallableModule('AppRegistry' in node_modules, if you find more than one, that's a likely reason

Answer 26 · 2020-01-15T21:39:30.000Z

@Hugo-Meiring Probably you use modules that were removed from react-native.
For example ViewPagerAndroid

This was the issue for us - we jumped from RN 0.58 to RN 0.61.5 where some RN stock components were removed. ViewPagerAndroid, AsyncStorage, ListView were the culprits for us.

Answer 27 · 2020-01-19T10:36:52.000Z

I face same problem just now and try any suggestion but noting change 😢

when I remove my computer everywhere node_modules I resolve this issue for me!!!
(because my disk will full)

so I guess maybe are multiple versions of react-native in node_modules ?

my steps

sudo find . -name "node_modules" -type d -prune -exec rm -rf '{}' +
reinstall yarn
run yarn in my porject
xcode -> clean build folder
iOS APP is working!!!!

Answer 28 · 2020-01-29T15:14:42.000Z

i had the same problem, when i used react-navigation package, but i had not downloaded all the required "side-packages" (particularly is react-native-reanimated). The problem may come from one of your import. Check the guide of all packages carefully, you would definitely find a way. Good luck!!

Answer 29 · 2020-02-15T13:40:52.000Z

Também deparei com isso (configuração abaixo). Peguei um pouco da solução do @ m4rcoperuano e parei meu simulador e empacotador, depois removi tudo no watchman via watchman watch-del-all. Reiniciei o simulador via react-native run-iose tudo funciona bem.

Configuração
react-native-cli: 2.0.1
react-native: 0.61.2
mac OSmojave 10.14.6

it worked for me

Answer 30 · 2020-02-19T17:12:45.000Z

cd ios
remove pods
pod install
worked for me

Answer 31 · 2020-02-28T18:11:05.000Z

who have this problem in Android mono repo (I have not tried this with ios): as @msand mentioned the problem could be in many registerCallableModule('AppRegistry' in your result bundle. Multiple occurrences could be because of using react-native components from other monorepo packages.

So we need to remove them from the bundle:

react-native run-android
Download bundle (from http://127.0.0.1:8081/index.bundle?platform=android&dev=true&minify=false), open it and inspect for the discussing substring
Now we need to block node_modules loading from the found places except the first one
Add into metro.config.js into resolver / blacklistRE patterns like this
blacklistRE: /(.*\\component1\\node_modules\\.*|.*\\component2\\node_modules\\.*|.*\\component3\\node_modules\\.*)$/
start again
react-native run-android
check bundle again, it should contain only one registerCallableModule('AppRegistry'
check how code works on a device.

in gap 4) you probably need to make more particular regexes if your components use "nohoist" components.

as a bonus - smaller bundle size. :)

Answer 32 · 2020-03-05T21:31:11.000Z

who have this problem in Android mono repo (I have not tried this with ios): as @msand mentioned the problem could be in many registerCallableModule('AppRegistry' in your result bundle. Multiple occurrences could be because of using react-native components from other monorepo packages.

So we need to remove them from the bundle:

react-native run-android

Download bundle (from http://127.0.0.1:8081/index.bundle?platform=android&dev=true&minify=false), open it and inspect for the discussing substring

Now we need to block node_modules loading from the found places except the first one

Add into metro.config.js into resolver / blacklistRE patterns like this
blacklistRE: /(.*\\component1\\node_modules\\.*|.*\\component2\\node_modules\\.*|.*\\component3\\node_modules\\.*)$/

start again
react-native run-android

check bundle again, it should contain only one registerCallableModule('AppRegistry'

check how code works on a device.

in gap 4) you probably need to make more particular regexes if your components use "nohoist" components.

as a bonus - smaller bundle size. :)

module.exports = {
  ...
  resolver: {
    blacklistRE: /(.*\/component\/node_modules\/.*)$/,
  },
 ... 
};

Answer 33 · 2020-03-20T18:44:24.000Z

It appears that delaying the first call to AppRegistry.registerComponent() until an asynchronous event occurs is sufficient to cause this problem. I have originally run into it due to a call to fetch() but it reproduces with something as simple as the default application created by react-native init if you change
AppRegistry.registerComponent(appName, () => App);
to
setTimeout( () => AppRegistry.registerComponent(appName, () => App), 0 );
Notably, changing setTimeout() to setImmediate() in the above example made the issue go away for me.

Answer 34 · 2020-03-31T12:46:38.000Z

just try yarn/npm install in your root folder of project 🤔

Answer 35 · 2020-04-04T22:49:23.000Z

I got the same issue when I added a 3rd party library with components. The root of the problem was that the library includes react, react-native, react-navigation as direct dependencies ("dependencies" field in package.json). After moving these dependencies to "peerDependencies" field of library package.json the error gone.

Answer 36 · 2020-04-16T11:21:19.000Z

Simple close the metro shell and re-run app.

Answer 37 · 2020-04-16T12:59:55.000Z

Getting the same issue, in a monorepo where my redux logic lives in a shared module alongside a react-dom and react-native project ... commenting out my imports doesn't seem to change anything but the error does disappear if I comment out the redux I'm trying to render ... anyone got any clues?? As a newbie to react-native and monorepos this whole process has been a NIGHTMARE 😭

Answer 38 · 2020-04-17T17:26:11.000Z

@lukecaan look into metro's blackList. With that you can make your app not seeing redundant libraries under redux's node_modules Ref: https://stackoverflow.com/questions/41813211/how-to-make-react-native-packager-ignore-certain-directories

Answer 39 · 2020-04-21T14:38:54.000Z

I've spent a decent time figuring out what's causing this error, but still the same.
I closed the metro bundler and ran: npm start and it worked, this is weird.

Answer 40 · 2020-04-24T03:57:50.000Z

It appears that delaying the first call to AppRegistry.registerComponent() until an asynchronous event occurs is sufficient to cause this problem. I have originally run into it due to a call to fetch() but it reproduces with something as simple as the default application created by react-native init if you change
AppRegistry.registerComponent(appName, () => App);
to
setTimeout( () => AppRegistry.registerComponent(appName, () => App), 0 );
Notably, changing setTimeout() to setImmediate() in the above example made the issue go away for me.

I am also a bug caused by asynchrony！

Answer 41 · 2020-04-26T17:30:00.000Z

I had the same issue for IOS, which appeared to pop up out of nowhere. Unfortunately, like @ralph-dev, I found the only thing that worked was going through every import statement to discover the faulty import.

Answer 42 · 2020-04-30T12:17:07.000Z

It worked for me this way. Just terminated the metro and reran yarn ios.

Answer 43 · 2020-05-13T15:12:30.000Z

Also try Android Studio: File > Sync Project with Gradle Files, it worked for me. 🎉

Answer 44 · 2020-05-14T02:35:16.000Z

Just run npm install then
re-run npm install -g react-native-cli , it worked for me

Answer 45 · 2020-05-31T21:01:47.000Z

Why does it have to be so difficult to find out WHICH Native Module cannot be null?

Exactly....After a long frustrating period, I decided to understand what does it mean actually. As far as I understand it is trying to tell that some npm package is identified in your node modules and it's not just enough to install the package but you have to add some code in ios in order to make that package works.

In my case I have installed npm package of react-native-push-notifications and done all the required changes in android but not in IOS. my ios app which used to work fine suddenly started giving me this clueless error. Finally, I have solved it. thanks to everyone.

Answer 46 · 2020-06-09T20:29:12.000Z

On iOS we followed @MaxMotovilov's suggestion about problems with delaying calling AppRegistry.registerComponent(appName, () => App). When we no longer waited for other components to load, all was good

Prev

async () => {
  await analytics.setup();
  AppRegistry.registerComponent(appName, () => App);
};

Working

() => {
  analytics.setup().catch(/* */);
  AppRegistry.registerComponent(appName, () => App);
};

Answer 47 · 2020-06-12T13:51:56.000Z

Hi

I had this exception too. I solved my problem.

What is problem?

RN has Message Queue which tries to dynamically dispatch a message AppRegistry::runApplication. In my case Message Queue did not have key "AppRegistry" associated with object AppRegistry. App threw exception Invariant Violation: Module AppRegistry is not a registered callabel module (calling runApplication).

Why it happened?

After You import AppRegistry You have to call any method,

import { Text, AppRegistry } from 'react-native';

const App = (props) => (
  <View>
    <Text>App1</Text>
  </View>
);

AppRegistry.registerComponent('Appname', () => App);

because it has getter which lazy loads real app registry module

 get AppRegistry(): AppRegistry {
    return require('./Libraries/ReactNative/AppRegistry');
  },

and this module is added to to MessageQueue

BatchedBridge.registerCallableModule('AppRegistry', AppRegistry);

Why I had this problem?

I inherited some codebase with async registration of components, which did not made AppRegistry to be added to MessageQueue sooner than event AppRegistry::runApplication fired .

How did I fix this?

Since it does not matter what method of AppRegistry I call, something like this on will do

// call this as soon as possible so AppRegistry is available to RN MessageQueue
AppRegistry.registerComponent('DummyComponent', () => DummyComponent);

How would I fix this?

I can't edit Your docs, so I can only hint: I would add to documentation that it is required to trigger loading of app registry and that it is
I would probably add it to https://reactnative.dev/docs/appregistry , but there seems to be no Hello World code which is not aimed at Expo so I would create a Hello World page for it (You can have Hello World by running react-native init, but it is not explained)
Or better, I would stop magically lazy loading stuff and ideally introduced init methods

Thanks

Answer 48 · 2020-06-16T07:05:33.000Z

For us, the error happens because one of our components in the top-level router is not written correctly, so there are multiple errors in the log. This error happens to be the last one thus we ignored the prior error. We found this out by reading the entire log from bottom to top.

Answer 49 · 2020-06-30T09:38:49.000Z

Try:

unlink the packages you've done manually
cd ios && rm -rf Pods && pod cache clean --all && pod install && cd .. (@djohnsonkc)
close the metro shell and re-run app. (@alitele)

Answer 50 · 2020-07-04T02:57:25.000Z

i had the same problem, when i used react-navigation package, but i had not downloaded all the required "side-packages" (particularly is react-native-reanimated). The problem may come from one of your import. Check the guide of all packages carefully, you would definitely find a way. Good luck!!

hello let's be friends! Could you please give me your facebook profile!

Answer 51 · 2020-07-06T07:58:46.000Z

@hcminhit not cool man

Answer 52 · 2020-07-14T21:42:29.000Z

Upgrating from react-native:"0.62.2" to "0.63.1" give me this error.

For me it's imposible to upgrade react-native without getting an error. It's amazing..

Answer 53 · 2020-07-14T22:24:07.000Z

I had to close metro and run expo start again. And it worked.

Answer 54 · 2020-07-20T16:26:15.000Z

you sure have probleme in an import that was not installed correct or that you have to reinstall your node modules

Answer 55 · 2020-07-23T07:21:39.000Z

I've had this issue multiple times and in every one of them I used a different solution. I always come here, like a retard, see that it's a vague error and end up just digging around my code and ultimately finding something dumb that I've done that broke my app. This last time, I had literally no idea what could be wrong. So I just ran pod install and npm install. Restarted the server, rebuilt the projects and it worked... MAGIC!

Answer 56 · 2020-07-23T09:28:27.000Z

I've had this problem when one of the dependencies was specified incorrectly and it led to two instances of react-native being installed in node_modules

Answer 57 · 2020-07-28T15:44:40.000Z

I'm updating a quite large project from 0.61 to 0.63 and I'm running into this issue.

I've extracted from our code all the imports we do from react-native:

require("react-native").View;
require("react-native").StyleSheet;
require("react-native").PixelRatio;
require("react-native").Dimensions;
require("react-native").Text;
require("react-native").Image;
require("react-native").TouchableOpacity;
require("react-native").KeyboardAvoidingView;
require("react-native").ScrollView;
require("react-native").TouchableWithoutFeedback;
require("react-native").Modal;
require("react-native").Switch;
require("react-native").FlatList;
require("react-native").ToastAndroid;
require("react-native").Alert;
require("react-native").NativeEventEmitter;
require("react-native").AppState;
require("react-native").ActivityIndicator;
require("react-native").ProgressBarAndroid;
require("react-native").RefreshControl;
require("react-native").Linking;
require("react-native").TouchableHighlight;
require("react-native").Share;
require("react-native").Animated.View;
require("react-native").Animated;
require("react-native").Animated.Value;
require("react-native").BackHandler;
require("react-native").Keyboard;
require("react-native").Vibration;
require("react-native").ImageBackground;
require("react-native").SafeAreaView;
require("react-native").Slider;
require("react-native").TextInput;

Do you see any of them that would cause this error?

If it's not there, then it is perhaps on the other react-native modules sigh...

Answer 58 · 2020-07-28T17:41:56.000Z

I'm updating a quite large project from 0.61 to 0.63 and I'm running into this issue.

I've extracted from our code all the imports we do from react-native:

require("react-native").View;
require("react-native").StyleSheet;
require("react-native").PixelRatio;
require("react-native").Dimensions;
require("react-native").Text;
require("react-native").Image;
require("react-native").TouchableOpacity;
require("react-native").KeyboardAvoidingView;
require("react-native").ScrollView;
require("react-native").TouchableWithoutFeedback;
require("react-native").Modal;
require("react-native").Switch;
require("react-native").FlatList;
require("react-native").ToastAndroid;
require("react-native").Alert;
require("react-native").NativeEventEmitter;
require("react-native").AppState;
require("react-native").ActivityIndicator;
require("react-native").ProgressBarAndroid;
require("react-native").RefreshControl;
require("react-native").Linking;
require("react-native").TouchableHighlight;
require("react-native").Share;
require("react-native").Animated.View;
require("react-native").Animated;
require("react-native").Animated.Value;
require("react-native").BackHandler;
require("react-native").Keyboard;
require("react-native").Vibration;
require("react-native").ImageBackground;
require("react-native").SafeAreaView;
require("react-native").Slider;
require("react-native").TextInput;

Do you see any of them that would cause this error?

If it's not there, then it is perhaps on the other react-native modules sigh...

It is probably race condition.

Add some code which imports AppRegistry and calls any of AppRegistry methods (Why? Because when some method of AppRegistry is called, AppRegistry is loaded and initialized).

Then please tell us if Your problem was fixed.

Answer 59 · 2020-07-29T00:04:22.000Z

Havig the same issue here 😭
Saludos desde Guatemala 🇬🇹

Answer 60 · 2020-07-29T06:23:06.000Z

@marcofuentes05 you are not having the same issue... In your case, just restart the metro bundler and you'll be OK...

Answer 61 · 2020-07-29T06:37:32.000Z

It is probably race condition.

Add some code which imports AppRegistry and calls any of AppRegistry methods (Why? Because when some method of AppRegistry is called, AppRegistry is loaded and initialized).

Then please tell us if Your problem was fixed.

@xchmelmilos you were right. I've added this:

import {AppRegistry} from 'react-native';
console.log('getAppKeys()=',AppRegistry.getAppKeys());

At the very beginning of my index.js file and the error is gone...

I'm a bit puzzled here:
-> I did not need to do that with RN 0.61.
-> I do not use AppRegistry directly as I am using react-native-navigation...

So I guess I should now try to identify which call where causing this race condition right?

With react native navigation alone, I do not get this error. So there is something in our code that get executed before RNN and after startup, that causes it...

If you have any hint/suggestion on how to proceed faster and more reliably to find it, please do not hesitate to tell me...

Once again thanks for your help @xchmelmilos!

Edit: for anyone using RNN, there is this issue there which is related.

Answer 62 · 2020-07-30T09:29:18.000Z

It is probably race condition.
Add some code which imports AppRegistry and calls any of AppRegistry methods (Why? Because when some method of AppRegistry is called, AppRegistry is loaded and initialized).
Then please tell us if Your problem was fixed.

@xchmelmilos you were right. I've added this:
import {AppRegistry} from 'react-native';
console.log('getAppKeys()=',AppRegistry.getAppKeys());
At the very beginning of my index.js file and the error is gone...

I'm a bit puzzled here:
-> I did not need to do that with RN 0.61.
-> I do not use AppRegistry directly as I am using react-native-navigation...

So I guess I should now try to identify which call where causing this race condition right?

With react native navigation alone, I do not get this error. So there is something in our code that get executed before RNN and after startup, that causes it...

If you have any hint/suggestion on how to proceed faster and more reliably to find it, please do not hesitate to tell me...

Once again thanks for your help @xchmelmilos!

Edit: for anyone using RNN, there is this issue there which is related.

It is caused by RN itself, You just have to be faster to initialize this than RN internal message queue tries to access it - I wrote about it here #26687 (comment) .

Answer 63 · 2020-07-30T14:59:22.000Z

@xchmelmilos actually, I thought the error was gone but it is not. I'm still seeing it in my logcat logs... Even with the addition to the index.js file I've made.

I'm a bit clueless on this one...

Answer 64 · 2020-07-30T15:08:50.000Z

It is a bit of black magic in my opinion because here what I exactly observe:

-> Without the index.js hotfix (pre-loading AppRegistry as you'b-ve suggested), I see the error both in logcat and in the RN logbox (dev mode):

2020-07-30 17:00:38.083 31128-31620/my.app I/ReactNativeJS: AppNavigation.hx:75: AppNavigation.init()
2020-07-30 17:00:38.156 31128-31620/my.app I/ReactNativeJS: AppNavigation.hx:233: setNavigationStack
2020-07-30 17:00:38.190 31128-31128/my.app E/unknown:ReactNative: ReactInstanceManager.attachRootViewToInstance()
2020-07-30 17:00:38.191 31128-31128/my.app E/unknown:ReactRootView: runApplication: call AppRegistry.runApplication
2020-07-30 17:00:38.193 31128-31128/my.app E/unknown:ReactNative: ReactInstanceManager.attachRootViewToInstance()
2020-07-30 17:00:38.193 31128-31620/my.app I/ReactNativeJS: Running "Home" with {"initialProps":{"componentId":"Component5"},"rootTag":111}
2020-07-30 17:00:38.193 31128-31128/my.app E/unknown:ReactRootView: runApplication: call AppRegistry.runApplication
2020-07-30 17:00:38.217 31128-31128/my.app E/unknown:ReactNative: ReactInstanceManager.attachRootViewToInstance()
2020-07-30 17:00:38.218 31128-31128/my.app E/unknown:ReactRootView: runApplication: call AppRegistry.runApplication
2020-07-30 17:00:38.983 31128-31620/my.app I/ReactNativeJS: Running "SideMenu" with {"initialProps":{"componentId":"drawer-id"},"rootTag":121}

-> With the fix, I see it only in logcat (not in logbox anymore):

2020-07-30 17:04:13.591 31128-31832/my.app I/ReactNativeJS: AppNavigation.hx:75: AppNavigation.init()
2020-07-30 17:04:13.625 31128-31832/my.app I/ReactNativeJS: AppNavigation.hx:233: setNavigationStack
2020-07-30 17:04:13.643 782-31866/? E/ResolverController: No valid NAT64 prefix (244, <unspecified>/0)
2020-07-30 17:04:13.664 31128-31128/my.app E/unknown:ReactNative: ReactInstanceManager.attachRootViewToInstance()
2020-07-30 17:04:13.665 31128-31128/my.app E/unknown:ReactRootView: runApplication: call AppRegistry.runApplication
2020-07-30 17:04:13.666 31128-31832/my.app I/ReactNativeJS: Running "Home" with {"initialProps":{"componentId":"Component5"},"rootTag":151}
2020-07-30 17:04:13.667 31128-31128/my.app E/unknown:ReactNative: ReactInstanceManager.attachRootViewToInstance()
2020-07-30 17:04:13.668 31128-31128/my.app E/unknown:ReactRootView: runApplication: call AppRegistry.runApplication
2020-07-30 17:04:13.689 31128-31128/my.app E/unknown:ReactNative: ReactInstanceManager.attachRootViewToInstance()
2020-07-30 17:04:13.690 31128-31128/my.app E/unknown:ReactRootView: runApplication: call AppRegistry.runApplication
2020-07-30 17:04:14.164 31128-31832/my.app I/ReactNativeJS: Running "SideMenu" with {"initialProps":{"componentId":"drawer-id"},"rootTag":161}

I do not see any significant difference in the logcat output :(...

Answer 65 · 2020-07-30T20:23:31.000Z

It is a bit of black magic in my opinion because here what I exactly observe:

-> Without the index.js hotfix (pre-loading AppRegistry as you'b-ve suggested), I see the error both in logcat and in the RN logbox (dev mode):

2020-07-30 17:00:38.083 31128-31620/my.app I/ReactNativeJS: AppNavigation.hx:75: AppNavigation.init()
2020-07-30 17:00:38.156 31128-31620/my.app I/ReactNativeJS: AppNavigation.hx:233: setNavigationStack
2020-07-30 17:00:38.190 31128-31128/my.app E/unknown:ReactNative: ReactInstanceManager.attachRootViewToInstance()
2020-07-30 17:00:38.191 31128-31128/my.app E/unknown:ReactRootView: runApplication: call AppRegistry.runApplication
2020-07-30 17:00:38.193 31128-31128/my.app E/unknown:ReactNative: ReactInstanceManager.attachRootViewToInstance()
2020-07-30 17:00:38.193 31128-31620/my.app I/ReactNativeJS: Running "Home" with {"initialProps":{"componentId":"Component5"},"rootTag":111}
2020-07-30 17:00:38.193 31128-31128/my.app E/unknown:ReactRootView: runApplication: call AppRegistry.runApplication
2020-07-30 17:00:38.217 31128-31128/my.app E/unknown:ReactNative: ReactInstanceManager.attachRootViewToInstance()
2020-07-30 17:00:38.218 31128-31128/my.app E/unknown:ReactRootView: runApplication: call AppRegistry.runApplication
2020-07-30 17:00:38.983 31128-31620/my.app I/ReactNativeJS: Running "SideMenu" with {"initialProps":{"componentId":"drawer-id"},"rootTag":121}

-> With the fix, I see it only in logcat (not in logbox anymore):

2020-07-30 17:04:13.591 31128-31832/my.app I/ReactNativeJS: AppNavigation.hx:75: AppNavigation.init()
2020-07-30 17:04:13.625 31128-31832/my.app I/ReactNativeJS: AppNavigation.hx:233: setNavigationStack
2020-07-30 17:04:13.643 782-31866/? E/ResolverController: No valid NAT64 prefix (244, <unspecified>/0)
2020-07-30 17:04:13.664 31128-31128/my.app E/unknown:ReactNative: ReactInstanceManager.attachRootViewToInstance()
2020-07-30 17:04:13.665 31128-31128/my.app E/unknown:ReactRootView: runApplication: call AppRegistry.runApplication
2020-07-30 17:04:13.666 31128-31832/my.app I/ReactNativeJS: Running "Home" with {"initialProps":{"componentId":"Component5"},"rootTag":151}
2020-07-30 17:04:13.667 31128-31128/my.app E/unknown:ReactNative: ReactInstanceManager.attachRootViewToInstance()
2020-07-30 17:04:13.668 31128-31128/my.app E/unknown:ReactRootView: runApplication: call AppRegistry.runApplication
2020-07-30 17:04:13.689 31128-31128/my.app E/unknown:ReactNative: ReactInstanceManager.attachRootViewToInstance()
2020-07-30 17:04:13.690 31128-31128/my.app E/unknown:ReactRootView: runApplication: call AppRegistry.runApplication
2020-07-30 17:04:14.164 31128-31832/my.app I/ReactNativeJS: Running "SideMenu" with {"initialProps":{"componentId":"drawer-id"},"rootTag":161}

I do not see any significant difference in the logcat output :(...

I do not see any errors in your listing, I see only information that AppRegistry.runApplication was called - which is ok. Have You pasted correct listings?

Answer 66 · 2020-07-31T06:52:03.000Z

@xchmelmilos excuse me you are right again, the following error log appears without preloading AppRegistry:

2020-07-31 08:48:10.091 1874-2153/my.app E/ReactNativeJS: Invariant Violation: Module AppRegistry is not a registered callable module (calling runApplication), js engine: hermes

I was mistaken because ReactRootView: runApplication: call AppRegistry.runApplication is a E error log and I was interpreting it as an error while it is probably not one.

So all is good, you hotfix works indeed. But shouldn't it be fixed right within RN?

Answer 67 · 2020-07-31T09:46:15.000Z

Got similar to @zabojad problem. After implementing a fix suggested, got this:

ExceptionsManager.js:179 Invariant Violation: "NavBarTextButton" has not been registered. This can happen if:
* Metro (the local dev server) is run from the wrong folder. Check if Metro is running, stop it and restart it in the current project.
* A module failed to load due to an error and `AppRegistry.registerComponent` wasn't called.

Not ideal, but leads me to a direction which component may actually cause a problem.

Edit:

Finally fixed it. For me it was an order in which appState.registerComponent was called. For some reason, after reloading, Navigation.events().registerAppLaunchedListener was called after MessageQueue call.

Put components registration code first thing in index.js and error has gone.

This

import {AppRegistry} from 'react-native';
console.log('getAppKeys()=',AppRegistry.getAppKeys());

allowed me to find a core problem, so give it a try. It may work for you.

React Native: 0.63.1
RNN: 6.6.0-snapshot.989

Answer 68 · 2020-07-31T12:03:12.000Z

@xchmelmilos excuse me you are right again, the following error log appears without preloading AppRegistry:
2020-07-31 08:48:10.091 1874-2153/my.app E/ReactNativeJS: Invariant Violation: Module AppRegistry is not a registered callable module (calling runApplication), js engine: hermes
I was mistaken because ReactRootView: runApplication: call AppRegistry.runApplication is a E error log and I was interpreting it as an error while it is probably not one.

So all is good, you hotfix works indeed. But shouldn't it be fixed right within RN?

Yes, this magical lazy loading of AppRegistry is nonsense, it should be explicit call like initializeAppRegistry() or initializing AppRegistry immediately when import is called.

Answer 69 · 2020-08-01T08:09:56.000Z

For my case I had to upgrade react-native-progress.
oblador/react-native-progress#201 (comment)

Answer 70 · 2020-08-04T16:19:03.000Z

Even after using the AppRegistry lazy-loading workaround it doesn't work for me.
It seems to crash when using react-navigation's createStackNavigator and other such methods.
Just upgraded from RN 0.61.5 to 0.63.2, had no issues before.

Answer 71 · 2020-08-05T00:39:29.000Z

Fixed the issue on my end by double checking that i modified all the files correctly during my RN upgrade, then running watchman watch-del-all, and react-native start --reset-cache. Then on android, build -> clean. then it worked! sigh

That worked for me.
Thanks

Answer 72 · 2020-08-05T12:38:41.000Z

I am also facing issue with React Navigation with reference to stack other methods. Mine is new project it was working yesterday suddenly stopper tried all the above mentioned steps but nothing worked for me.

RN info -

System:
    OS: macOS 10.15.3
    CPU: (8) x64 Intel(R) Core(TM) i7-7820HQ CPU @ 2.90GHz
    Memory: 86.23 MB / 16.00 GB
    Shell: 5.7.1 - /bin/zsh
  Binaries:
    Node: 12.18.2 - /usr/local/bin/node
    Yarn: 1.7.0 - /usr/local/bin/yarn
    npm: 6.14.5 - /usr/local/bin/npm
    Watchman: 4.9.0 - /usr/local/bin/watchman
  IDEs:
    Android Studio: 3.6 AI-192.7142.36.36.6241897
    Xcode: /undefined - /usr/bin/xcodebuild
  npmPackages:
    react: 16.13.1 => 16.13.1 
    react-native: 0.63.2 => 0.63.2 
  npmGlobalPackages:
    react-native-cli: 2.0.1
    react-native-git-upgrade: 0.2.7
    react-native: 0.61.5

Answer 73 · 2020-08-08T13:54:35.000Z

In our case, there was a bug in a function that was being called at the global level in a module, i.e., at module load time. We had something like this in foo.js:

export default (a, { param }) => {
...

and then in bar.js we had something like this:

import foo from './foo.js'
foo('something')

i.e., called foo() at the top level of the module but without the final argument. I doubt it was specific to this particular bug, but the crash at module load time was probably enough to derail the AppRegistry.

Answer 74 · 2020-08-09T15:28:26.000Z

Ok guys, here we are my solution for this issue:

npm install native-base@latest -g
npm install react-native@latest -g
change package.json for these dependencies
delete node_modules and npm install

Open it Xcode and Build/Run from scratch

I hope it helped

Answer 75 · 2020-08-13T23:04:29.000Z

Probably the single most vague, annoying error in the react-native environment... And we know there's a lot of them :)

Usually I'm getting it after adding a package via yarn add. Not sure if it's connected to yarn itself and whether npm fixes it. In my case the fix is to remove node_modules and reinstall them, but then again... it's after every package add/remove I do, which can be very annoying and time consuming.

Answer 76 · 2020-08-18T06:48:58.000Z

I spent a few hours having the same issue Invariant Violation: Module AppRegistry is not a registered callable module (calling runApplication) and it happened "from nowhere".

Because everything was working fine in the previous day and everything was still working fine in the production bundle I thought the usual YOLO commands delete, clean and re-install everything would fix it but I was wrong.

Turns out it was one of the imports (as some suggested above). I couldn't believe it because this package/import has been in the project for weeks 🤕

Answer 77 · 2020-08-20T15:29:33.000Z

Like @weblancaster, I've recieved this error from nothing. Some days ago I had a good-working app, but suddenly this error appeared, though I didn't install any modules or changed anything. I've tried to reinstall node modules, clean cache, re-link libraries but nothing helped.

Answer 78 · 2020-08-21T04:54:08.000Z

@amphyxs take a look at your imports or any small bug that could have been introduced in the past days. Turns out the error message is pretty vague and could be anything but the actual AppRegistry call.

Answer 79 · 2020-08-22T18:01:13.000Z

I was having this issue on iOS and not Android. This made me think it was likely a bad module install for the iOS platform. After some debugging I found out it was react-native-unimodules. I had set it up badly setup on iOS.

Now that in itself may be useful, but likely not. I'd like to share my approach, as that is more useful.

Start in App.tsx and start cutting components/children out one by one until it builds something successfully.
(I placed a dummy <View> with a <Text> so I knew when it was successful.)
Once its loaded - add the offending component/line back in, and let FastRefresh reload your app.
In my case - and I hope in your case too - the error will now be different! This is because the initial App registration was complete, and FastRefresh must work a different way.
Look at the error - hopefully it's useful! (Mine mentioned unimodules - aha!)

That made then finding the issue a lot lot simpler.

Best of luck! 🤞🏼

Answer 80 · 2020-08-24T00:11:51.000Z

Downgraded back from 0.63.2 to 0.61.5.....fixed the problem.
Hopefully RN team will address this with next release and then Ill upgrade again

Answer 81 · 2020-09-03T00:38:56.000Z

I found that I had a small piece of styling that was missing a letter, and that caused this error to pop up. I had "alignConten" instead of "alignContent", and just adding that 't' fixed the error. I sincerely hope everyone was having different, and more relevant issues underlying their errors...

Answer 82 · 2020-09-03T22:36:49.000Z

Encountered this issue after upgrading to 0.63.2, commenting out the imports did eventually help as I was able to see some additional error logs. I had 3 libraries giving me issues.

"react-native-paper": "^4.1.0", // forced to update from 2.15.2
"react-navigation-material-bottom-tabs": "^2.3.0", // forced to update from 1.0.0
"react-native-material-textfield": applied this patch https://stackoverflow.com/a/62794092/12843101

Answer 83 · 2020-09-06T21:32:21.000Z

Check if you don't have this situation:

/folder/index.js

export * from './a'
export * from './b'

/folder/a

export function a(){
//...
}

/folder/b

export function a(){ //instead of b()
//...
}

When trying to import the modules exported with the same name, it gives this error.

Answer 84 · 2020-09-07T12:12:29.000Z

Apparently I started getting this error after an unsuccessful npm installation of css-to-react-native

Edite: Restarting all programs does solve the issue but don't know the root of the problem.

Answer 85 · 2020-09-12T13:27:47.000Z

I really don't know how to explain, but for me, when this happens, I just close everything (Visual Studio, Android Studio, Emulators) and reopen them. After that, my app starts to work again. It´s very weird but I got this Module AppRegistry error many times and every time I restarted all the programs, my app "came back to life". It doesn't hurt to try!

Answer 86 · 2020-09-25T16:44:20.000Z

Close everything: Server, VS Code, Emulator, Rebuild the by --reset-cache command, and run your app. If still persists, try restarting the system and doing the steps once more.

https://stackoverflow.com/a/51304124/11667949

https://stackoverflow.com/a/46826116/11667949

Answer 87 · 2020-09-26T18:20:40.000Z

I reverted to react-native 0.62.0 from 0.63.2. At least 0.62.0 shows some information that which component has the problem. Then I able to fix the issue related to the component. Hopes in the future update we will get more information about the issue in the log.

Answer 88 · 2020-09-28T22:31:04.000Z

For ios i've only intalled pod, the command i recommend is:
cd ios; pod install; cd ..
I consider that this is produced when i installed react-navigation on my node_modules, and then i forgot to install the pod files related to this new dependency.
Then hit on clear build, close and open xcode and run

Answer 89 · 2020-10-02T09:30:33.000Z

In case this helps... I resolved this on Android by manually registering some ReactPackage's, despite the instructions of ReactNative and ReactNative-Firebase against that ( https://rnfirebase.io/migrating-to-v6 )
I added:

    .addPackage(new ReactNativeFirebaseAppPackage())
    .addPackage(new ReactNativeFirebaseCrashlyticsPackage())

It may be relevant that I also register other packages manually - like MainReactPackage, but also MyAppReactPackage, RNRecyclerviewListPackage etc. No idea if the extra ones are compliant with auto-linking or whatever else.

My dependencies are:

      "@react-native-firebase/app": "^8.4.5",
      "@react-native-firebase/crashlytics": "^8.4.9",
      "react": "16.9.0",
      "react-native": "0.61.5",

(gradle) 
      val firebase = "17.5.0"
      crashlytics = "17.2.2"
      crashlyticsPlugin = "2.3.0"

P.S. It's probably a stupid way to solve the problem, and I probably have lots of inconsistencies in my setup. At some point it's just trial and error now...

Answer 90 · 2020-10-05T06:38:00.000Z

for me expo r -c cleared cache then restart the application worked perfectly for me

Answer 91 · 2020-10-09T06:27:02.000Z

So I have been roped back into this project because the issue was resurfaced again. The initial issue was eventually resolved by:

Creating a new react native project from scratch with the exact same name but the latest version (and git init it + commit). This is useful to see what changes between the latest init project that attempts to copy parts of the broken one.
Slowly add all the libraries to the package.json and keep testing which broke and which didn't, using the latest of each where possible. And get it to just show the default hello world screen without issue with all the libraries.
Add all the source code and update all breaking changes + refactor where needed. I did it first for the inner react native project, and then once it worked did it for our main project. This eventually allowed both iOS and Android to run 0.61.X
Copy over this working project over the broken project (remember don't copy over / delete the .git folder of either project). Commit and you are good to go.

I love @ralph-dev 's fastest way suggestion and agree. We will take that route first. That should work, then we can update to react native 0.63.x. Else we will need to do the above like previously. Will report back. All the other suggestions have been tried by the dev that took over from me.

Final note, to those that find this. Especially with some very complex issues, ones where the compilers fail because of a compiler bug, no output or stack trace is given or the crash is not even in any code remotely related or identifiable to you, where Google has no results (not even in Chinese, google translate is amazing and has helped immensely) and there is no smart strategy the way I found to solve the issue as last resort is a binary search. Keeping dividing your code into half (not literally) and disable the one "half". Keep doing this until you hit the issue. It grows exponentially and you will soon get to the issue within 8 - 20 levels deep.

Answer 92 · 2020-10-12T17:24:55.000Z

I solved this problem by removing a dependency and an instance that I had made, but I forgot to remove these 2 lines of code

Answer 93 · 2020-10-23T15:21:43.000Z

this error occurs when you add dependency without linking it with react-native link, to fix this you need to remove the dependency, reinstall it and link it with react-native link

(there are only certain dependencies that must be linked)

Answer 94 · 2020-10-28T23:54:08.000Z

I ran into this issue when updating to RN 0.63.3, we figured out it was because we were importing a library which had a dependency on an older version of react, hence two react native versions were being loaded into the yarn lockfile.

Could be something for you guys to check out - take a look at the lockfile and ensure there's only one version of react native in there.

Answer 95 · 2020-11-06T06:38:58.000Z

I am facing this issue many times. why Facebook is not taking it seriously.

can anyone tell how to fix this?

Answer 96 · 2020-11-09T09:42:19.000Z

I had the same problem when updating to RN 0.63.3.
And it work for me by adding the code
"resolutions": {
"@react-native-community/viewpager": "4.1.0",
"react-native-webview": "10.10.0",
}

Answer 97 · 2020-11-10T07:22:55.000Z

I had the same problem when updating to RN 0.63.3.
And it work for me by adding the code
"resolutions": {
"@react-native-community/viewpager": "4.1.0",
"react-native-webview": "10.10.0",
}

Where can I use this code?

Answer 98 · 2020-11-12T02:07:53.000Z

I had the same problem when updating to RN 0.63.3.
And it work for me by adding the code
"resolutions": {
"@react-native-community/viewpager": "4.1.0",
"react-native-webview": "10.10.0",
}

Where can I use this code?

package.json

Answer 99 · 2020-11-12T21:49:03.000Z

As commented before, it's quite a generic error.

Remove the node_modules folder and then run yarn install or npm install

it seemed to solve the issue here.

Answer 100 · 2020-11-16T03:29:04.000Z

Another possible reason for this is that there are multiple versions of react-native in node_modules

thank for insight