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
ping @janicduplessis I'm wandering if you have noticed this issue, the native implementation is removed in RN0.44, and the Native Animated version works great if the dataSource is initialized and won't be changed in the future, but if it's bean changed, the sticked header will become unstick
I remember you've made a commit to the master to resolve this kind of issue for SectionList on Android, but I haven't tried it yet, not sure if it happens on Android still
The text was updated successfully, but these errors were encountered:
Closefacebook#13500
I've been bothered by this issue for quite a long time, finally get some time to look into this.
I find the root cause is that after the props of the native driven node is assigned with a plain value, if you set it to a `Animated.Value` again, it's won't take any effect any more, so I make it to be a `Animated.Value` all the time
`value --> Animated.Value (✅) --> value (✅)) --> Animated.Value (❌)`
ping @janicduplessis
nihgwu
added a commit
to nihgwu/react-native
that referenced
this issue
May 10, 2017
Platform: iOS
RN version: 0.44.0-rc.0
ping @janicduplessis I'm wandering if you have noticed this issue, the native implementation is removed in RN0.44, and the Native Animated version works great if the dataSource is initialized and won't be changed in the future, but if it's bean changed, the sticked header will become unstick
I remember you've made a commit to the master to resolve this kind of issue for
SectionList
on Android, but I haven't tried it yet, not sure if it happens on Android stillThe text was updated successfully, but these errors were encountered: