Invariant Violation: "main" has not been registered. This can happen if:
Personne n'a encore pris cette issue.
- Langage dominant
- C++
- Étoiles
- 127k
- Forks
- 25.3k
- Merge moyen
- 1 j 23 h
- PR mergées (30 j)
- 4
Description
Description
I have run the react native project for android and got the error on the emulator screen just after opening it.
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., js engine: hermes
Steps to reproduce
Install application and yarn android.
React Native Version
0.79.5
Affected Platforms
Runtime - Android
Output of npx @react-native-community/cli info
System:
OS: Windows 11 10.0.26100
CPU: (20) x64 13th Gen Intel(R) Core(TM) i7-13650HX
Memory: 18.30 GB / 39.69 GB
Binaries:
Node:
version: 22.14.0
path: C:\nvm4w\nodejs\node.EXE
Yarn:
version: 1.22.22
path: C:\nvm4w\nodejs\yarn.CMD
npm:
version: 10.9.2
path: C:\nvm4w\nodejs\npm.CMD
Watchman: Not Found
SDKs:
Android SDK:
API Levels:
- "34"
- "35"
Build Tools:
- 34.0.0
- 34.0.0
- 34.0.0
- 34.0.0
- 35.0.0
- 35.0.0
- 35.0.0
- 35.0.0
- 35.0.0
- 35.0.1
- 36.0.0
System Images:
- android-34 | Google APIs Intel x86_64 Atom
- android-34 | Google Play Intel x86_64 Atom
- android-35 | Google Play Intel x86_64 Atom
- android-35 | Pre-Release 16 KB Page Size Google Play Intel x86_64 Atom
- android-36 | Google APIs Intel x86_64 Atom
- android-36 | Google Play Intel x86_64 Atom
- android-36 | Pre-Release 16 KB Page Size Google APIs Intel x86_64 Atom
Android NDK: Not Found
Windows SDK: Not Found
IDEs:
Android Studio: AI-243.24978.46.2431.13363775
Visual Studio: Not Found
Languages:
Java:
version: 17.0.10
path: /c/Program Files/Java/jdk-17/bin/javac
Ruby: Not Found
npmPackages:
"@react-native-community/cli":
installed: 18.0.0
wanted: ^18.0.0
react:
installed: 19.0.0
wanted: 19.0.0
react-native:
installed: 0.79.5
wanted: 0.79.5
react-native-windows: Not Found
npmGlobalPackages:
"*react-native*": Not Found
Android:
hermesEnabled: true
newArchEnabled: false
iOS:
hermesEnabled: Not found
newArchEnabled: Not found
info React Native v0.81.1 is now available (your project is running on v0.79.5).
info Changelog: https://github.com/facebook/react-native/releases/tag/v0.81.1
info Diff: https://react-native-community.github.io/upgrade-helper/?from=0.79.5&to=0.81.1
info For more info, check out "https://reactnative.dev/docs/upgrading?os=windows".
Stacktrace or Logs
09-09 19:19:29.561 4602 4779 E ReactNativeJS: ReferenceError: Property 'document' doesn't exist, js engine: hermes
09-09 19:19:29.580 4602 4779 I ReactNativeJS: Running "main" with {"rootTag":11}
09-09 19:19:29.582 4602 4779 E ReactNativeJS: Invariant Violation: "main" has not been registered. This can happen if:
09-09 19:19:29.582 4602 4779 E ReactNativeJS: * 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.
09-09 19:19:29.582 4602 4779 E ReactNativeJS: * A module failed to load due to an error and `AppRegistry.registerComponent` wasn't called., js engine: hermes
MANDATORY Reproducer
...
Screenshots and Videos
Guide de contribution
Ouvrir le guide de contribution
Par où commencer
- Lisez l'issue en entier, puis le guide de contribution du projet.
- Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
- Forkez le dépôt et travaillez sur une branche.
- Ouvrez une pull request qui référence le numéro de l'issue.
Piste de recherche
Commencez par reproduire le problème avec yarn android et examinez l’erreur Hermes précédente, en particulier ReferenceError: Property 'document' doesn't exist ; vérifiez que Metro est lancé depuis le dossier du projet et retracez le module qui échoue avant AppRegistry.registerComponent. C’est terminé lorsque la cause de l’échec est confirmée et qu’un correctif reproductible a été trouvé, ou qu’il est documenté que le problème provient de l’application.
Rédigé par le modèle d'indexation à partir du texte de l'issue.
Évaluation
- Stack technique
- android, react-native
- Domaine
- mobile-dev
- Type d'issue
- Bug
- Difficulté
- 4/5
- Temps estimé
- 3-5 jours
- Activité
- Active
- Clarté
- À clarifier
- Accessibilité débutants
- 28/100