You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Running latest ReactXp (v 2.0.0). I set up a basic animated View component to test some things I am seeing. I found that if I add two animated value styles to the same component, one that is native animatable (eg, opacity) and one that is not (eg, top), and then try to animate only the former (opacity) with useNativeDriver: true, it fails on iPad with the error "Style property 'top' is not supported by native animated module". This is despite the fact that top is not being animated. NO animation is being run on the 'top' value at all (both are present because different actions could animate one or the other, they never animate together and in fact I've taken out the portion of the code that would animate top, so it currently never animates). This seems very wrong as the value being animated IS native animatable and should be able to run with native drivers.
The text was updated successfully, but these errors were encountered:
Running latest ReactXp (v 2.0.0). I set up a basic animated View component to test some things I am seeing. I found that if I add two animated value styles to the same component, one that is native animatable (eg, opacity) and one that is not (eg, top), and then try to animate only the former (opacity) with useNativeDriver: true, it fails on iPad with the error "Style property 'top' is not supported by native animated module". This is despite the fact that top is not being animated. NO animation is being run on the 'top' value at all (both are present because different actions could animate one or the other, they never animate together and in fact I've taken out the portion of the code that would animate top, so it currently never animates). This seems very wrong as the value being animated IS native animatable and should be able to run with native drivers.
The text was updated successfully, but these errors were encountered: