Warning: ScrollView doesn't take rejection well - scrolls anyway

[donghanji]

When used the react-native-scrollable-tab-view,use nested,like this:

class TabView extends Component {
  render() {
    var self=this;
    return (
      <ScrollableTabView
        tabBarPosition={'bottom'}
      >
        <View style={styles.container} tabLabel="View 1">
          <Text style={styles.welcome}>
            Welcome to React Native 1!
          </Text>
        </View>
        <ScrollableTabView
          tabLabel="View 2"
          >
          <View style={styles.container} tabLabel="View 2.1">
            <Text style={styles.welcome}>
              Welcome to React Native 2.1!
            </Text>
          </View>
          <View style={styles.container} tabLabel="View 2.2">
            <Text style={styles.welcome}>
              Welcome to React Native 2.2!
            </Text>
          </View>
        </ScrollableTabView>
        <View style={styles.container} tabLabel="View 3">
          <Text style={styles.welcome}>
            Welcome to React Native 3!
          </Text>
        </View>
      </ScrollableTabView>
    );
  }
}

Will get the warning message:ScrollView doesn't take rejection well - scrolls anyway

Debug in Chrome,this is throw with "ScrollResponder.js",its "scrollResponderHandleResponderReject" method.This is its comments and the "scrollResponderHandleResponderReject" method:

  /**
   * Invoke this from an `onResponderReject` event.
   *
   * Some other element is not yielding its role as responder. Normally, we'd
   * just disable the `UIScrollView`, but a touch has already began on it, the
   * `UIScrollView` will not accept being disabled after that. The easiest
   * solution for now is to accept the limitation of disallowing this
   * altogether. To improve this, find a way to disable the `UIScrollView` after
   * a touch has already started.
   */
  scrollResponderHandleResponderReject: function() {
    warning(false, "ScrollView doesn't take rejection well - scrolls anyway");
  },

It said,the solution for now is to accept the limitation of disallow this altogether.

Is there an other better way to solve this problem here?

[skv-headless]

#187

[donghanji]

Others have encountered this issue,
see here,facebook/react-native#1501

[skv-headless]

facebook/react-native@5f77f15

[skv-headless]

I think it is fixed