-
-
Notifications
You must be signed in to change notification settings - Fork 414
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
Expo SDK 52 upgrade breaks animations #561
Comments
Same here. After upgrading to Expo SDK 52 and rn reanimated to 3.16.1 (as required per Expo), experiencing the identical issue. It's reproducible in a fresh new barebones project. |
This mainly because of new arch, you can set newArchEnabled to false so the animation works normally |
Unfortunately, that does not solve it @shorkyyy. It was the first thing I tried when I ran into the issue and I just retried it again. I ensured that I ran a clean build by resetting everything, and both issues I described above still persist. |
Same problem here. "react-native-draggable-flatlist": "^4.0.1", |
Same problem here. "react-native-draggable-flatlist": "^4.0.1", 0.5x iPhone.16.Pro.Video.Speed.Change.Nov.21.mp4 |
+1 for the video @Unuuuuu, this is exactly what I am seeing as well |
Also I'm seeing a lot of console errors during the dragging.
|
Yes @fonodi I am seeing the same. You can silence these warnings for the meantime, but I bet they are somehow involved in this behavior |
Haven't tested on sdk52 yet but I have tested it on sdk51 and when I enable newarch, the same issue appears and I had no clue what's wrong with it, so I cloned my project and set newarch = false and the issue disappears |
I have similar glitches in the same situation on sdk 52 with the new architecture enabled. When I disable the new architecture it works much better but still I get the same messages as @fonodi :
|
I am also having issues since upgrading to EXPO SDK 52. This setup doesnt work anymore. The animations are broken and I am getting this error: (NOBRIDGE) ERROR Warning: ref.measureLayout must be called with a ref to a native component. |
Managed to fix the same issue in my project with this patch, please check if it helps. |
I applied your patch, now It's not so horrible, but I still can see some glitches... |
@ddrozdov thank you for the patch! I went ahead and applied it and as @aleksey-mukho noted, there has been an improvement but not all the way. In detail: The Bad: However, now the items themselves very briefly flash on rearrange. Sometimes multiple items, not just the ones being dragged. To me this suggests that the draggable flatlist is being re-rendered. The Ugly: The resizing issue is still present, and I still cannot reproduce it consistently. Sometimes I will drag an item and it will drop down and resize down correctly. Other times, I will drag and drop, but the item never resizes down again. |
Hi @computerjazz Your project is amazing, but I think everyone is missing you 😃 Could you tell us what your plans are with the project? |
He mentioned his plans here #542 (comment) |
Has anyone managed to solve the problem? |
I have identified the cause of the problem. In the CellRenderer Component, the transform style is updated while the element is being moved. |
@kristof-kovacs I just noticed the same when in |
It didn't help me (( |
Based on this patch: computerjazz#561 (comment)
@ddrozdov this actually helped for me as well for one moment, but then it reverted to the same behavior. So unfortunately not this did not fix it. However, I still am running into the issue of some of the items that I move are resized wrong and do not size down after drag |
I also have the same problem. Even in the example, empty app. Should I try downgrading the Expo version? |
Describe the bug
After an upgrade to Expo SDK version 52, and all relevant dependencies, a previously working horizontal draggable flatlist exhibits two incorrect behaviors:
Full code of the component is attached below.
Platform & Dependencies
Please list any applicable dependencies in addition to those below (react-navigation etc).
Previous Platform & Dependencies where this code worked
The text was updated successfully, but these errors were encountered: