Closed
Labels
BugComponent: SectionListStaleThere has been a lack of activity on this issue and it may be closed soon.There has been a lack of activity on this issue and it may be closed soon.
Description
I cannot use the reference method ScrollToLocation on a nested Section List. It will always give me error saying that this._scrollRef.scrollTo is not a function. (In 'this._scrollRef.scrollTo(o?{x:y,animated:p}:{y:y,animated:p})', 'this._scrollRef.scrollTo' is undefined). I am using RN 0.59.9.
React Native version:
info
React Native Environment Info:
System:
OS: Windows 10
CPU: (8) x64 Intel(R) Core(TM) i7-8550U CPU @ 1.80GHz
Memory: 2.98 GB / 7.87 GB
Binaries:
Yarn: 1.16.0 - C:\Program Files (x86)\Yarn\bin\yarn.CMD
npm: 6.4.1 - C:\Program Files\nodejs\npm.CMD
IDEs:
Android Studio: Version 3.4.0.0 AI-183.6156.11.34.5522156
Steps To Reproduce
- Using the provided expo
- Click on one not bold item.
- No using the provided expo
- Setup one SectionList component
- On the section List renderItem, render another SectionList component
- On the second secondList, capture its reference
- Call scrollToLocation method of the second sectionlist on renderItem click.
E expect the list to scroll to the index provided on the section provided
Snack, code example, or link to a repository:
Reacted by Davit Voskanyan
Metadata
Metadata
Assignees
Labels
BugComponent: SectionListStaleThere has been a lack of activity on this issue and it may be closed soon.There has been a lack of activity on this issue and it may be closed soon.
Activity
andercard commentedon Jun 18, 2019
It happens to me the same error is as if the method did not exist
stale commentedon Sep 16, 2019
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.
stale commentedon Sep 23, 2019
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.