-
-
Notifications
You must be signed in to change notification settings - Fork 403
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
TypeError: Cannot assign to read-only property 'current' #496
Comments
Same for me |
In case this helps someone else: I was experiencing similar "read-only property" exceptions after I updated react-native-draggable-flatlist from version 3.1.1 to 4.0.1. At the same time I also updated React Native, react-native-reanimated, and many other modules — so lots of changes. I was able to fix the problem by wrapping my app content in a <GestureHandlerRootView> and taking into account some <DraggableFlatList> changes including removing an obsolete ListHeaderComponent prop. |
Had the same issue after updating to RN 0.72 (I was already on the latest version of reanimated and RNGH). I could pinpoint it to the |
I also mitigated the same issue by downgrading the react-native version to version 0.71.8 (and expo to 48.0.20). |
@robrechtme 's suggestion worked for me. Issue was with ListFooterComponent, which is described here: I used the alternative () => notation he mentioned and things worked. Good temporary workaround until that's fixed. |
For me, the error was similar:
I am on
And the error for me is iOS-only! Using
instead of
fixed the error for me. |
My error was "cannot assign to read-only property 'validated' but the solution was the same
|
Having the same error. The issue is passing a component input
And the reason I can't use arrow function is because when the component rerenders from the
I tried I also tried to replicate the error on snack.expo.dev but I cannot get 4.0.1 to work. Using 3.1.2, there was no error. |
I had the same issue with |
The fix can be found here in PR 484 |
Facing issue here in the below link. Not able to pass components directly and getting locked with re-render issue |
Describe the bug
Hello,
Since I updated to React Native 0.72.3, I encountered this error when I rerender a screen with a DraggableFlatlist:
It was working fine on React Native 0.71.6. I also updated Reanimated from version 2.14.4 to 3.4.1 and react-native-gesture-handler from version 2.9.0 to 2.12.1.
I have tried everything I can, but it seems the problem is within the component.
The first render works correctly, but if I come back to the screen or update a state that triggers a rerender of the component, it crashes with this error.
To Reproduce
Platform & Dependencies
The text was updated successfully, but these errors were encountered: