You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The RefreshControl documentation doesn't mention that when the component is wrapped in a custom compoent it needs props passed so that it doesn't break on Android.
What is the problem?
If you have a component like this
<Container
......
refreshControl={}
the dev has no way to know that the refreshControll prop returns props that need to be passed down to the RefreshControl in you custom component in order for it to work on Android.
We fixed it by passing props to the custom component and then to RefreshControll. This issue was present only on Android and it was breaking the entire screen.
How can we address it?
Include a note in the RefreshControl documentation that mentions this issue.
Why is it important?
This will save debugging time for developers.
Who needs this?
Devs developing for Android
When should this happen (use version numbers if needed)
This isn't time sensitive but the sooner - the better.
The text was updated successfully, but these errors were encountered:
Description
The RefreshControl documentation doesn't mention that when the component is wrapped in a custom compoent it needs props passed so that it doesn't break on Android.
What is the problem?
If you have a component like this
<Container
......
refreshControl={}
the dev has no way to know that the refreshControll prop returns props that need to be passed down to the RefreshControl in you custom component in order for it to work on Android.
We fixed it by passing props to the custom component and then to RefreshControll. This issue was present only on Android and it was breaking the entire screen.
How can we address it?
Include a note in the RefreshControl documentation that mentions this issue.
Why is it important?
This will save debugging time for developers.
Who needs this?
Devs developing for Android
When should this happen (use version numbers if needed)
This isn't time sensitive but the sooner - the better.
The text was updated successfully, but these errors were encountered: