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] FabricViewStateManager: setState called without a StateWrapper #32070
Comments
same here on 0.65, error is incredibly crypted, google returns really few results. |
Yeah, I had this problem too. I downgraded to 0.64.2 and it stopped crashing. :) Don't know what's wrong with the 65 though, I liked it a lot until it started crashing. |
@gigadeplex it's not only on 0.65.x, it happened to me on 0.64.x too, it would be great if someone from facebook team explain why this is throwing. In my case it won't crash the app |
same here |
The same thing just happened to me, after installing react navigation drawer and reanimated 2, now the app crashes and the screen goes blank, help me |
facing the same issue can someone help please |
I solved it by migrating my logic to a new project of react native 0.65.1 with the latest versions of react navigation |
same issue |
same here |
1 similar comment
same here |
My app uses RN 0.65.1 with react-native-reanimated v2.2.2 and it was facing this issue on android. I updated react-native-reanimated to v2.3.0-beta.2 and in my initial testing I cannot replicate this issue now. |
+1 same issue, any solutions except upgrading to 2.3.x ? |
I was also facing this issue, I was using @react-navigation/stack. "@react-navigation/drawer": "^6.1.8", happy coding. all the best. |
same here! |
same problem |
Just import the hooks from the navigation/native not from the core. Like useRoute, useNavigation, usScrollToTop |
Which hooks? All my used useState Hooks? |
same problem |
I got the same both on Android and iOS, the "solution" I had was to call |
For me this error shows up when I import a TextInput component. I'm on RN version 0.67.0 and it maches the screen shot in this issue #32114 |
Ok, my issue wasn't the same as this one please view #31572 for a workaround |
it seem that it happened when ReactScrollView updateStateOnScroll |
The error message will show when scrolling Flatlist. |
This same error to showed my logcat. But I worked on Curved navigation bar, after routing not worked and crashed and showed this error.. |
any progress in this issue? |
I'm also experiencing the same issue, after debugging, here's the flow that originates the issue:
Because the
This is the flow that I've seen in a project I'm working on. I have the following questions:
|
Any update on this issue? I can run my app of the Expo platform without any issues, however when I am running it on the emulator it starts throwing this error and app stops working properly. Stuck for a few days, please help. |
any updates on this issue? |
Any Update on This Issue, It Still Occurs from Me Also |
This is happening for me, seeing the error |
Happening for me on Android app launch |
same here, any update? |
1 similar comment
same here, any update? |
This is happening to us as well - we have the following dependencies that may be relevant:
|
According to this, it looks like react-native-reanimated is not adding support for Fabric until v3. Not sure if that's what is behind all this but it could be. I'm not sure why the error mentions Fabric when it should be disabled though 🤔 |
any update on this?
|
I ma facing the same issue. Any Update? I am using: "react-native": "0.66.5",
"react-native-gesture-handler": "2.9.0",
"react-native-reanimated": "^3.3.0",
"react-native-safe-area-context": "^4.5.3",
"@react-navigation/bottom-tabs": "^6.4.1",
"@react-navigation/compat": "^5.3.20",
"@react-navigation/drawer": "^6.4.4",
"@react-navigation/native": "^6.0.12",
"@react-navigation/stack": "^6.2.3", |
@cortinico Are you guys looking into this issue, as this still happening on latest 0.72.1 with android. |
This issue is stale because it has been open 180 days with no activity. Remove stale label or comment or this will be closed in 7 days. |
This issue was closed because it has been stalled for 7 days with no activity. |
@cortinico The issue is not yet resolved! It shouldn't be closed as it's still happening and we didn't get any explanation for the behaviour at all. |
Please open a new issue and provide a valid reproducer, then we can look into it 👍 |
Fair enough, I totally agree with you. But It's very hard to reproduce this since it's only happening on production track + it happens with some users only (not all of them). We only get reports from the Google play console about the crashes with stack trace of the crash (along with device model and brand). The only pattern I've noticed in my case, is that it happens only with the newest Android APIs (30 up to 34) not lower. I was trying to reproduce this on my own many times, But I don't know where to start debugging for the issue or what to expect and what not or where to look and focus. In many cases the App is stuck on Splash screen after fresh install, or it opens then immediately crashes and never opens again. which doesn't happen to me at all when I try it myself (I tried many devices, but no luck). |
Please provide all the information requested. Issues that do not follow this format are likely to stall.
Description
i have no idea what is wrong , but i app get stuck and logcat print
FabricViewStateManager: setState called without a StateWrapper
repeatedlyReact Native version:
Run
react-native info
in your terminal and copy the results here.Steps To Reproduce
Provide a detailed list of steps that reproduce the issue.
Expected Results
Describe what you expected to happen.
Snack, code example, screenshot, or link to a repository:
Please provide a Snack (https://snack.expo.io/), a link to a repository on GitHub, or provide a minimal code example that reproduces the problem.
You may provide a screenshot of the application if you think it is relevant to your bug report.
Here are some tips for providing a minimal example: https://stackoverflow.com/help/mcve
The text was updated successfully, but these errors were encountered: