Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Re-renders affects the behavior of the animations (2.0.0-alpha.6)
See original GitHub issueDescription
If you run setInterval at the same time as the animation, the animation does not work properly.
In my app, I used setInterval for counting up seconds at the same time as the movement animation. It worked with reanimated 2.0.0-alpha.5 properly. But with 2.0.0-alpha.6, it doesn’t work well.
Screenshots
| no setInterval | with setInterval |
|---|---|
 |
 |
Steps To Reproduce
Call setInterval(() => {}, 1000) at the same time as the movement animation
Expected behavior
Animations should work well.
Actual behavior
Animations doesn’t work properly
Snack or minimal code example
https://github.com/gaishimo/reanimated-2-playground-1/blob/set-interval-problem/src/App.tsx
If my use of setInterval is not good, I would be happy to get some advice.
Package versions
- React: 16.13.1
- React Native: 0.63.1
- React Native Reanimated: 2.0.0-alpha.6
Issue Analytics
- State:
- Created 3 years ago
- Comments:7 (4 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
I understand the current useSharedValue behavior. Thanks.
If a situation in which I want to disable this behavior comes up with, I’ll let you know.
From my POV I think it’s better for DX when we prioritize intuitive behavior over performance. Your both solutions sound great, I’m personally more fond of deps one but both are good.
Resolved, so closing.