Invariant Violation: "main" has not been registered.
See original GitHub issueJust updated expo-cli and initialized a new project with the TypeScript Tabs template. I did not touch the code. Navigated to the project’s directory and ran yarn start and was met with this error:
Invariant Violation: “main” 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.
Tried to resolve by using registerRootComponent, but that is not working either.
Issue Analytics
- State:
- Created 3 years ago
- Reactions:8
- Comments:23 (7 by maintainers)
Top Results From Across the Web
Invariant Violation: "main" has not been registered
The main reason to get this error is that, for some reason, App.js is not functioning properly.
Read more >"Application has not been registered" error
Your app root component may not be registered ... Another possibility is that there is a mismatch between the AppKey being provided to...
Read more >has not been registered. this can happen if: * metro (the local ...
Invariant Violation: "main" has not been registered. This can happen if: Metro (the local dev server) is run from the wrong folder. Check...
Read more >Invariant Violation Main Has Not Been Registered | Expo Drawer
ReactNativeDrawer#invariantViolationMainHasNotBeenRegistered,#invariantViolationReactNative,#failedToInitializeReactNativeReanimatedLibrary ...
Read more >invariant violation main has not been registered react-native
Application main has not been registered. Hint: This error often happens when you're running the packager (local dev server) from a wrong folder....
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 upgraded my projects to sdk 38.0.8. I get the same issue.
having same issue after my upgrade from 37 to 38.0.8