Upgrading to 6.13.0 from 6.12.0 breaks the build
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 7.2k
- Forks
- 748
- Avg merge
- 2d 18h
- Merged PRs (30d)
- 1
Description
Description
I just upgraded from 6.12.0 to 6.13.0 and getting the following exception from Metro on launch:
ERROR Invariant Violation: Tried to register two views with the same name HighlighterView, js engine: hermes
ERROR Invariant Violation: Module AppRegistry is not a registered callable module (calling runApplication). A frequent cause of the error is that the application entry file path is incorrect.
Related to
- Components
- Demo
- Docs
- Typings
Steps to reproduce
- Update the package version in package.json to 6.13.0
- Run yarn
- Run react-native start --reset-cache
- Launch App.
Expected behavior
Bundle loads successfully and App launches as usual
Actual behavior
The following error post compilation:
ERROR Invariant Violation: Tried to register two views with the same name HighlighterView, js engine: hermes
ERROR Invariant Violation: Module AppRegistry is not a registered callable module (calling runApplication). A frequent cause of the error is that the application entry file path is incorrect.
More Info
The error goes away when I roll-back to 6.12.0
The project is on React Native 0.66.4 (Non Expo)
Code snippet
Screenshots/Video
Environment
- React Native:
- React Native UI Lib:
Affected platforms
- [ X ] Android
- iOS
- Web
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the failure by upgrading from 6.12.0 to 6.13.0, running yarn, resetting the Metro cache, and launching the Android app on React Native 0.66.4 with Hermes. Start by tracing the duplicate HighlighterView registration reported by Metro. Done means the app launches successfully on 6.13.0 without either invariant violation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- react-native
- Domain
- mobile-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100