Jumpy scroll when inverted and contains a section footer

[AndrewJack]

Environment

 React Native Environment Info:
    System:
      OS: macOS High Sierra 10.13.6
      CPU: x64 Intel(R) Core(TM) i7-4770HQ CPU @ 2.20GHz
      Memory: 227.11 MB / 16.00 GB
      Shell: 5.3 - /bin/zsh
    Binaries:
      Node: 10.10.0 - /usr/local/bin/node
      Yarn: 1.9.4 - /usr/local/bin/yarn
      npm: 6.4.1 - /usr/local/bin/npm
      Watchman: 4.9.0 - /usr/local/bin/watchman
    SDKs:
      iOS SDK:
        Platforms: iOS 11.4, macOS 10.13, tvOS 11.4, watchOS 4.3
      Android SDK:
        Build Tools: 23.0.1, 23.0.2, 23.0.3, 24.0.0, 24.0.1, 24.0.2, 24.0.3, 25.0.0, 25.0.1, 25.0.2, 25.0.3, 26.0.0, 26.0.1, 26.0.2, 26.0.3, 27.0.3, 28.0.2
        API Levels: 23, 25, 26, 27, 28
    IDEs:
      Android Studio: 3.1 AI-173.4819257
      Xcode: 9.4.1/9F2000 - /usr/bin/xcodebuild
    npmPackages:
      react: 16.5.0 => 16.5.0 
      react-native: 0.57.0 => 0.57.0 
    npmGlobalPackages:
      react-native-cli: 1.0.0

Description

Inverted SectionList is jumpy when scrolling, then if you scroll back down the content disappears.

This commit e0c7363 caused this issue, reverting this fixes the problem. cc @rbrosboel

Example:

    <SectionList
        sections={sections}
        renderItem={this.renderItem}
        keyExtractor={this.keyExtractor}
        renderSectionFooter={this.sectionFooter}
        ListFooterComponent={this.sectionFooter}
        style={styles.list}
        inverted
      />

Steps

1. Scroll up a long way
2. Observe the indicator on the right jumps about more than usual
3. scroll back down fast
4. observe the list items disappear and the scroll view is blank

Reproducible Demo

Example can be found here in JumpyInvertedListBug.js. or run the project and observe.
https://github.com/AndrewJack/react-native-basic

[danilobuerger]

Possible duplicate of #20956

[stale]

Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community's attention? This issue may be closed if no further activity occurs. You may also label this issue as "For Discussion" or "Good first issue" and I will leave it open. Thank you for your contributions.

[stale]

Closing this issue after a prolonged period of inactivity. If this issue is still present in the latest release, please feel free to create a new issue with up-to-date information.