FlatList's initialScrollIndex causes problems with rendering new items

[Zygro]

Description

If I set InitialScrollIndex > 0 in a FlatList, new items render only after I scroll

React Native version:

System:
    OS: macOS 10.15.5
    CPU: (4) x64 Intel(R) Core(TM) i5-5257U CPU @ 2.70GHz
    Memory: 1.85 GB / 8.00 GB
    Shell: 5.7.1 - /bin/zsh
  Binaries:
    Node: 13.6.0 - /var/folders/2l/hq37k9yd2mx5kj_070z8n7zw0000gn/T/yarn--1594212746482-0.17054963075652996/node
    Yarn: 1.21.1 - /var/folders/2l/hq37k9yd2mx5kj_070z8n7zw0000gn/T/yarn--1594212746482-0.17054963075652996/yarn
    npm: 6.13.4 - /usr/local/bin/npm
    Watchman: 4.9.0 - /usr/local/bin/watchman
  Managers:
    CocoaPods: 1.7.4 - /Users/michalsmolik/.gem/ruby/2.7.0/bin/pod
  SDKs:
    iOS SDK:
      Platforms: iOS 13.5, DriverKit 19.0, macOS 10.15, tvOS 13.4, watchOS 6.2
    Android SDK:
      API Levels: 27, 28, 29
      Build Tools: 28.0.3, 29.0.0, 29.0.2
      System Images: android-21 | ARM EABI v7a, android-28 | Google APIs Intel x86 Atom, android-28 | Google Play Intel x86 Atom, android-29 | Google APIs Intel x86 Atom
      Android NDK: Not Found
  IDEs:
    Android Studio: 3.5 AI-191.8026.42.35.6010548
    Xcode: 11.5/11E608c - /usr/bin/xcodebuild
  Languages:
    Java: 1.8.0_232 - /usr/bin/javac
    Python: 2.7.16 - /usr/bin/python
  npmPackages:
    @react-native-community/cli: Not Found
    react: 16.11.0 => 16.11.0 
    react-native: 0.62.2 => 0.62.2 
  npmGlobalPackages:
    *react-native*: Not Found

Steps To Reproduce

Have a FlatList with initialScrollIndex > 0 and add item to it. This new item will be rendered only after scrolling the FlatList.

Expected Results

Item renders as soon as it is added

Snack, code example, screenshot, or link to a repository:

https://snack.expo.io/@zygroo/flatlist-initialscrollindex-bug

[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 a "Discussion" or add it to the "Backlog" and I will leave it open. Thank you for your contributions.

[AntoineDoubovetzky]

I believe this is now fixed (#33558)

[cortinico]

Yup thanks for pointing out @AntoineDoubovetzky. Closing