Skip to content
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] Invariant Violation: "this.props" should not be accessed during state updates #32

Open
stonehiy opened this issue Jul 24, 2024 · 6 comments

Comments

@stonehiy
Copy link

Verson info:
"react-native": "0.71.3",
"react-native-timer-picker": "^1.10.1",

When using TimePicker, a quick swipe will result in the following exception:

Invariant Violation: "this.props" should not be accessed during state updates
                                                                                                    
This error is located at:
in VirtualizedList
in FlatList
in RCTView
in Unknown
in Unknown
in RCTView
in Unknown
in Unknown
in RCTView
in Unknown
in RCTView
in Unknown
in AnimatedComponent
in AnimatedComponentWrapper
in Unknown
in RCTView
in Unknown
in RCTView
in Unknown
in AnimatedComponent
in AnimatedComponentWrapper
in ThemeProvider
in RCTView
in Unknown
in PortalManager
in Portal.Host
in RNCSafeAreaProvider
in SafeAreaProvider
in SafeAreaProviderCompat
in PaperProvider
in App
in RCTView
in Unknown
in ChildrenWrapper
in _default
in Root
in RCTView
in Unknown
in AppContainer, js engine: hermes, stack:
@troberts-28
Copy link
Owner

Hey @stonehiy,

Thanks for raising this. Will take a look ASAP and get this fixed 🙌

@troberts-28
Copy link
Owner

Hey @stonehiy, can you share your code please? Struggling to recreate this error without it.

@troberts-28
Copy link
Owner

Hey @stonehiy, thanks for sharing the demo. I'm still not seeing that error on my end but I had a suspicion of what might be causing it.

I've safeguarded against it in the latest version (v1.10.3). Please try upgrading to that version, and let me know if the error persists 🙌

@stonehiy
Copy link
Author

stonehiy commented Aug 5, 2024

Hey @stonehiy, thanks for sharing the demo. I'm still not seeing that error on my end but I had a suspicion of what might be causing it.

I've safeguarded against it in the latest version (v1.10.3). Please try upgrading to that version, and let me know if the error persists 🙌

Hey @troberts-28 ,I have tried to use the lasest version(v1.10.3), but this bug isn't fixed to me.

@troberts-28
Copy link
Owner

Ah ok, will have another go at recreating it and get back to you 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants