Stuck on an issue?

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.

useNativeDriver breaks functionality

See original GitHub issue

Since useNativeDriver: true is now in defaultProps, this https://github.com/facebook/react-native/issues/16218 has started to occur by default. Using useNativeDriver={false} works as expected. Probably a bug in react-native’s Animated API, but they’ve closed that issue even though it was not fixed. Unless there is a way to work around this, I’d suggest removing useNativeDriver from defaultProps. Maybe someone got it to work with the latest version?

Issue Analytics

State:
Created 4 years ago
Comments:9 (3 by maintainers)

Top GitHub Comments

1reaction

aboveyunhaicommented, Sep 4, 2020

Oh that might be the issue. I am trying to use useNativeDriver with all animations to lighten the JS thread.

Good to know.

Not only for this package, there are a lot of cases where useNativeDriver: true will crush your app especially playing around with react-native-svg. This option is not well supported AFAIK. You might be aware of that.

0reactions

williamgoodhewcommented, Sep 28, 2020

I am still getting this issue on Android using

“react-native”: “0.62.2”, “react”: “16.11.0”, “react-native-circular-progress”: “^1.3.6”,