fix: move requestAnimationFrame back to Reanimated #6991
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
I introduced a regression in #6973 by moving JS implementation of
requestAnimationFrame
to Worklets. Native version ofrequestAnimationFrame
is injected in Reanimated'sUIRuntimeDecorator.cpp
sorequestAnimationFrame
must be overwritten in Reanimated, not in Worklets.Since all the native implementation is in Reanimated and it would be a hard task to extract it right now, I decided to keep it for the time being unless we decide where it should land eventually.
Test plan
The only difference is the lack of batching with my regression introduced. You can
console.log(currentCallbacks.length)
to see that the batching is restored.