-
Notifications
You must be signed in to change notification settings - Fork 133
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
[0.0.18] invalid value passed to interaction #185
Comments
Hmm weird, thanks for sending. I haven't tried reanimated 2.5 yet, I wonder if that's related (I'm on 2.3). |
FYI: if you're using a custom-dev-client like I do, you will need to disable expo autolinking for rea inside the package.json since its not working with 2.5.0 currently.
|
I reproduced this in my app, will investigate. |
Dealing with reanimated internals is tricky! Think I got it, will push shortly. |
I am dealing with those internals since 3 days to fix an ugly bug but I am close to give up! |
Hm, reanimated may not allow this specific case for some reason. Going to try to repro and send a PR. Thought I had it working, might have been mistaken. |
It will work for the |
Here is a reproduction that shows it's not possible with Reanimated: https://snack.expo.dev/@beatgig/courageous-bubblegum Will open an issue there. |
Opened an issue: software-mansion/react-native-reanimated#3123 |
Closing for now since it's a reanimated issue. Will make a note of this on the canary release notes. |
Closing this will most likely cause duplicate reports, or? |
closing, as we're beholden to reanimated for this to work and it's documented that it isn't ready yet. |
Hi @nandorojo,
tried the Canary and so far, everything was working as expected without breaking changes.
While I tried your release-note example, which was looking dope, I encountered this issue:
Some informations:
The text was updated successfully, but these errors were encountered: