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

[Android] React Navigation Native Stack + Nativebase Flatlist #3952

Open
exneval opened this issue Aug 15, 2021 · 5 comments
Open

[Android] React Navigation Native Stack + Nativebase Flatlist #3952

exneval opened this issue Aug 15, 2021 · 5 comments
Labels

Comments

@exneval
Copy link
Contributor

exneval commented Aug 15, 2021

Describe the bug
Weird behavior with android FlatList when RefreshControl is enabled, as you go back from FlatList stack to the previous stack, a refresh icon showed up above. Tested without nativebase, there's no such a behavior.

To Reproduce
Steps to reproduce the behaviour:

  1. Use React Navigation Native Stack
  2. Use Nativebase
  3. Implement a FlatList with refresh control enabled
  4. The weird behavior happened

Expected behaviour
There's no refresh icon showed up

CodeSandBox/Snack link
snack.

Need help @intergalacticspacehighway

@exneval exneval added the v3 V3 label Aug 15, 2021
@exneval
Copy link
Contributor Author

exneval commented Aug 18, 2021

After some investigation, this behavior happened only if there's a component above the FlatList that has RefreshControl enabled, if I move that component into ListHeaderComponent prop, everything looks normal

But still I want my component above the FlatList to have fixed position, because If move it to ListHeaderComponent prop, the component will also be moved with scrolling

Updated:
I can use stickyHeaderIndices to make component in ListHeaderComponent have a fixed position (sticky)
But that's it, I don't know if you guys want to fix this because it's just an alternative way to avoid this happened, so I'll let this issue open

@Viraj-10
Copy link
Collaborator

Hi @exneval, Thanks for reporting this issue. We will look into it.

@stale
Copy link

stale bot commented Mar 19, 2022

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale label Mar 19, 2022
@exneval
Copy link
Contributor Author

exneval commented Mar 19, 2022

Still no news from @Viraj-10

@stale stale bot removed the stale label Mar 19, 2022
@stale
Copy link

stale bot commented May 25, 2022

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale label May 25, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants