-
-
Notifications
You must be signed in to change notification settings - Fork 417
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
Support react-native-reanimated 2 #247
Comments
The same problem |
@computerjazz is there any plans to rewrite the lib with reanimated v2, now that it is stable? |
@nelsonprsousa @computerjazz Hello, please take a look at this request. #270 |
Can't wait. Thanks for this cool lib. |
@nelsonprsousa I saw those warnings. This is because |
Okay, thank you @pirroman |
;) |
Wow, you rock 🚀 |
UPDATE: While migrating to reanimated 2 is in the long-term plan, v2 currently has performance issues when rendering lots of nodes. Until these are addressed, this package (as well as see: |
Will there be a beta using v2 that we can use if we want? |
v2 migration is on hold until the rewrite is released (#281) and the above performance issues are addressed. |
@computerjazz Quite confused, since package.json requires reanimated v2.0 or higher as a peer dependency? So if the migration is not ready, why did the peer deps get bumped? Not wanting to hijack this issue but when I use v2 I'm unable to drag on the iOS simulator on v2.6.2. Works perfectly fine with reanimated < 2.0.0 |
v2 peer dep shouldn't have been bumped, I will revert that. This package is currently compatible with BOTH v1 and v2, and v1 will be supported for the immediate future. The migration is completely separate from making the package compatible with v2. The purpose of the migration is to make this package actually use the new v2 apis. Since v2 is backwards compatible, we can still use the v1 apis. Not sure about that drag issue. please open a separate issue with a snack repro. |
Now it's 2022, what's the status of this issue? I wonder if Reanimated v2 is officially supported or not. I'm facing into the problem described by svenlombaert, which also appears in these issues:
Downgrading Reanimated to 1.13.4 worked for iOS but it breaks Android build (maybe due to compatibility with other packages), so I'm in a dead lock now. Is the codebase tested on Reanimated v2? |
I am using this library in the current latest version (3.0.6) with Reanimated (2.5.0) and it works. Some warnings related with react-native-gesture-handler are being generated, tho. @computerjazz know much better what's happening and the state of draggable-flatlist and REA v2 + RNGH. |
TLDR: I'm curious, this seems to be a common misconception that you cannot use reanimated v2 in a project with As far as upgrading to the v2 api ,we're in basically the same boat as we were when reanimated v2 launched. It's simply not performant enough to handle As far as the drag issue you're facing, please provide a repro snack/project and I'll look into it. |
Thanks, then there might be another factor I'm not aware of. I'm going to tinker around the dependencies further and try to create a repro.
My bad, in my case the misconception mostly came from the fact that this issue is still open and seemed to be inactive for several months. Another point is somone says “v1.13.3 is the latest working version with draggable flatlist” in the issues I listed above. |
Back then, on that version, the peer dependencies where just pinned wrongly and I had to install with the |
@computerjazz the issue with the item moving position on long press still exists. Note the issue only occurs after scrolling down the list. Scrolling to the top of the list and then dragging works fine. I have tried downgrading reanimated to 1.13.4 but that didn't work. Any idea? Dependencies: Code structure example: |
Describe the solution you'd like
We could take advantages of the new react-native-reanimated 2, already using Turbo Modules.
The text was updated successfully, but these errors were encountered: