-
Notifications
You must be signed in to change notification settings - Fork 582
Warning useNativeDriver and componentWillReceiveProps how to solve? #398
Comments
This has been mentioned quite a lot of time. Did you make any process, @ascoders ? I face the same issue |
|
Hey guys, I'm a new maintainer for this repo and I'm trying to resolve most common issues right now. Read more in #396. It still might take time to make into release, but at least I can say that next release is soon (like a week or so). I will notify people here to update once the new version is out. @GoktuqCan yeah, technically it is in the repo already, but it was not released to npm. So next version will have it. |
I have updated to 3.0.1 and found that this problem has been solved,thanks @ArtemKolichenkov |
I having upgraded to 3.0.1 and I am getting the Animated: useNativeDriver was not specified. I am trying to catch up on these notes, but wondering did anyone get rid of the useNativeDriver warning? |
I just upgraded the lib to 3.0.1 today and still get the warning
function shouldUseNativeDriver(
config: {...AnimationConfig, ...} | EventConfig,
): boolean {
if (config.useNativeDriver == null) {
console.warn(
'Animated: `useNativeDriver` was not specified. This is a required ' +
'option and must be explicitly set to `true` or `false`',
);
}
... |
If you're still getting the warning, check that it's coming from this library! It's possible that some other library is causing it. Also, if you're using |
Today (May 14th) I used this component for the first time,What went wrong?
The text was updated successfully, but these errors were encountered: