onStartReached isn't always called on reaching the start of the list
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 7.2k
- Forks
- 392
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 1
Description
Current behavior
The onStartReached callback isn't always called when the start of the list is reached. I have attached a project that reproduces a case where it's not called. Here onStartReached should trigger the loading of more data.
https://github.com/user-attachments/assets/901f763a-603f-45e8-b158-c385ad285953
Expected behavior
onStartReached should be called when the start of the list is reached.
To Reproduce
Use this project: FlashlistTestProject.zip
- Run on Android (
npm install && npm run android) - Select "Start at top"
- Scroll downwards until you reach the bottom
- Observe that the last item starts with "6 72 ..." and no more items load after that.
Platform:
- iOS (not tested)
- Android
Environment
FlashList 2.0 RC
React Native 0.80.1
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start from the onStartReached callback entry point and reproduce the Android case using the attached FlashlistTestProject.zip. Run npm install && npm run android, select "Start at top," and scroll to the bottom; done means the callback fires and more items load instead of stopping at the item beginning "6 72 ...".
Written by the indexing model from the issue text.
Assessment
- Tech stack
- react-native, typescript
- Domain
- mobile
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100