Tomasz Żelawski
Tomasz Żelawski
I'll look into this once I get my hands on the real device.
This is a tricky one - this is actually a problem with animation cancelling and the asynchronous nature of events. Each animation has properties `startTimestamp` and `lastTimestamp` - to track...
From my research it seems that (on the iOS simulator) re-opening a keyboard causes the UI to freeze for ~50ms. The interrupted animation doesn't know that the delay is "intentional"...
Hey @jbroma, sorry I missed your message. The API to use it isn't pretty unfortunately since it's handled during Babel transpilation. You can see it being used on my draft...
AFAIK in the new major version of NativeWind this won't be an issue. Falling back to the way the code was generated pre 4.1.1 is yielding more significant problems.
@marklawlor Could you weigh in here?
Hey @piotrski, this PR fixes this: https://github.com/software-mansion/react-native-reanimated/pull/6904 It's available in Reanimated 3.17.1 Could you please check if it works for you?
I have actually confirmed that this is a separate issue with the Compiler, unreleated to #6904
I opened an issue for the React Compiler https://github.com/facebook/react/issues/32580. Given it some thought it's actually impossible to fix it on our end.
@dennis-Softfruit at the moment no. The best workaround for now is to use `'worklet'` directives explicitly or add `'use no memo'` directive in troublesome components.