Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug] failed to scroll to selected alphabet after push navigation and go back #9

Open
calvinsug opened this issue Feb 27, 2020 · 4 comments

Comments

@calvinsug
Copy link

when i push navigation after select any listView and go back to alphabet list scroll view layout,

i cannot select my desire alphabet properly, when i select anything, it forces me to scroll to the most bottom user (with Z name)

@kmcgill88
Copy link

I am seeing this too. I noticed when I push navigation the scroll is disposed, usually.

My use case I have

Screen A -> list AZ screen -> screen C

Going A to list AZ push works great.

If I navigate to screen C and then back to AZ list...AZ state is gone. Then anything I try to drag AZ it always push to the bottom of list starting with Z.

@knyghtryda
Copy link

@calvinsug I'm having this exact same issue and have tried multiple versions of this library. I don't even have to push navigation, mine scrolls to Z no matter what I do!

@LiewJunTung
Copy link
Owner

Thanks for reporting. I'll check it out. It'll be most useful if you can provide an example app.

@kmcgill88
Copy link

I haven't found a fix but have narrowed this down to when this is happening in my app. When I push list AZ screen -> screen C, screen C is kicking off a network call using the http package. As soon as the network call is made the AZ list is disposed. I remove making the network call, the AZ list works as expected going to and from screen C without losing state.

🤷‍♂ Very confusing!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants