Mateusz Łopaciński

Ok, thanks @micahlt for letting me know. Please inform me once you find something out.

Hey guys! We are aware of the issue. It affects only the New Architecture so that's why switching back to the Old Architecture results in better scrolling performance. We are...

@NyoriK >The same code runs smoothly in Expo Go on both Android and iOS, despite Expo Go typically having more overhead than development builds. Interesting. I don't think there should...

@chanphiromsok Yeah, I know. We haven't released a fix yet. We started rewriting the core logic in reanimated which we hope to improve performance (at least a bit) and fix...

Hey @alessioemireni! This fix was mostly related to the v4 changes only and the code that was optimized doesn't exit in v3. If Reanimated `3.19.3` is taking too much time...

@alessioemireni I will discuss about this topic during the next week's meeting with a team. We will see if we can improve it somehow. I didn't see many people complaining...

Hey everyone! A quick update after the meeting. We’re all aware of the build time and package size issue, and we're planning to investigate it further. For now, we don’t...

As far as I know, we haven't added support for this property yet, so it gets sent to the native side as an unparsed string. We should add support for...

@dmarcucci > Trying to launch in Expo Go and the entire Expo Go app just crashes. Expo Go works only with specific versions of `react-native-reanimated` that are compatible with the...

@avele FYI, the `scheduleOnUI` is not an equivalent of the `runOnJS`. `scheduleOnUI` replaces the `runOnUI` (not JS) method whilst the `scheduleOnRN` is a replacement of the `runOnJS`.