fix: Chrome debugger crash caused by incorrect viewTag #6437
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
MatiPl01
commented
Aug 21, 2024
packages/react-native-reanimated/src/createAnimatedComponent/createAnimatedComponent.tsx
Outdated
Show resolved
Hide resolved
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
The problem was reported in this issue and this discussion seems to report the same problem.
In short, the crash was caused by incorrect check in
_getViewInfoincreateAnimatedComponentwhich assigned the_componentto theviewTagonly for web but not for chrome debugger. I replacedIS_WEBcheck withshouldBeUseWeb, which also checks whether the current environment is a chrome debugger.Test plan
npx @react-native-community/cli init ReactNativeDebugger --version 0.75.1react-native-debuggerand enabled remote debugging with js,