-
Notifications
You must be signed in to change notification settings - Fork 24.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Android v0.65.1] Fresh install gives NativeUIManager.getConstantsForViewManager('Text') error while debugging #32197
Comments
Downgrading to 0.64 also fixes the issue |
the same is happening to me after upgrading to 0.65.1 |
Same error after upgrading to 0.65.1 (from 0.63.3) |
same issue with rn v0.65.1 |
Is there any solution other than downgrade? |
The same here with v0.65.1 |
Same Issue With RN 0.65.1 :( |
Same error after upgrading to 0.65.1 (from 0.64.2). Any updates on how to solve it? |
+1 RN 0.65.1 |
2 similar comments
+1 RN 0.65.1 |
+1 RN 0.65.1 |
|
Guys, can you try this work around. That's fixed the issue for me, but keep in mind, that's must be a 'temporary fix', who are here since march, release after release, unfortunately. |
We believe #31164 fixed this, and will be in the v0.66 release (it is already in v0.66.0-rc.4) |
yes, I did this work around and posted this workaround on StackOverflow and made a PR #31153 but as @TheSavior said This would unexpectedly alter the behavior of an app between dev and prod |
same issue with rn v0.65.1 |
@sezginriggs I believe it was fixed for react-native 0.66 (will likely release any day now, rc4 from last week appears to be final) That's the commit that fixed it, it was in 0.66.0-rc.1 and should be released shortly. |
@shinken008 +1 comments are useless in practice and just add notifications noise to people trying to solve root causes. Please do not post them. Use a reaction (thumbs-up) in the future, thank you |
Can confirm, with react-native@0.66.0 this isn't an issue anymore. |
Found this on react-native@0.66.0 |
That's a very surprising result @nahidmbstu - triple-check everything's clean ( |
I can confirm I am also facing this issue on react native 0.66 unfortunately; has there been any progress on this since? |
This issue was definitively closed, with no successful reproductions after 0.66.0-rc.1 |
It is definitely an issue, however it seems to be related to react native reanimated v2 (https://docs.swmansion.com/react-native-reanimated/docs/#known-problems-and-limitations) |
That really sounds like a separate thing, this used to occur without reanimated. Same error may occur from multiple causes, the cause identified by this issue has been fixed |
i am still seeing this issue on react native version 0.68.1 but this is not a clean install. |
The way to know it's not from react-native is to try it on a clean install yes. This is the script I use for react-native release testing (and to qualify it for react-native-firebase to make sure I won't have support problems there) https://github.com/mikehardy/rnfbdemo/blob/main/make-demo.sh - it's the script I use along with the react-native-firebase e2e tests (which use javascript debugging interface) to say with certainty: it's fixed. I used to reproduce it. The PR was merged and released. I do not reproduce it. It's fixed. |
I'm on react-native 0.66.1 and I'm getting this error when trying to get size of topBar from react-native-navigation |
Description
Trying to create a new project with the the latest stable version of both RN and RN CLI throws this error when Debug mode is enabled:
Even if you just render a single View component with a Text inside WITH styling, it will throw the error.
IF you remove the style prop from the Text component then the error is gone.
React Native version:
Steps To Reproduce
react-native init testa
yarn start
andyarn android
Expected Results
Not throw any error
Snack, code example, screenshot, or link to a repository:
The text was updated successfully, but these errors were encountered: