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
Incompatibility with react-native-reanimated@3.3.0
#293
Comments
hmm and you rebuilt the dev client i assume? |
could it be a reanimated issue? all dripsy does is combine the style prop |
Yes |
I'd say so, but most of entry points from error stacktrace were pointing to memo-hash. I'll post error screenshot later today |
hard to say without a stack trace |
Hey @nandorojo! Sorry for the delay, including stack trace with a screenshot
|
looks like the error is caused by a date time picker? |
|
and removing styled() fixes it? |
i would want to make sure it’s isolated to dripsy somehow |
Yes, removing usage of dripsy in the whole component resolves the issue |
weird. i wonder if the animated view allows array style props still. a minimal repro would be easiest to debug for me. thanks! |
Will try to reproduce it later today |
Hey @nandorojo! Sorry for the delay with the reproduction, wasn't able to get to it, but now it's done |
@nandorojo any news here? |
I think it's possible that reanimated is completely highjacking the style prop. That said, if you're using Just do this: |
I'm mostly using |
Just for reference, I'd typically split out animated components from |
When I tried to upgrade from
react-native-reanimated@2.14.4
(officially supported by expo) toreact-native-reanimated@3.3.0
the development client failed to launch with errorreading from '_value' directly is possible only on UI thread
. The stacktrace was pointing to thecreateThemedComponent
. I'm usingAnimated.createAnimatedComponent
on some components withstyled
The text was updated successfully, but these errors were encountered: