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

[iOS][RefreshControl] broken after re-enter app #13977

Closed
fokoz opened this issue May 15, 2017 · 5 comments
Closed

[iOS][RefreshControl] broken after re-enter app #13977

fokoz opened this issue May 15, 2017 · 5 comments
Labels
Resolution: Locked This issue was locked by the bot.

Comments

@fokoz
Copy link

fokoz commented May 15, 2017

RefreshControl use with ListView stops spinning and gets stuck(refreshing=true) when go out and re-enter app(press home button and then re-enter app).
I also have tested on ActivityIndicator and it works fine.

Additional Information

React Native version: 0.43
Platform: iOS
Development Operating System: macOS
Device: Real Device iOS 10

@flyskywhy
Copy link
Contributor

If your project use code-push before rn 0.43, you need upgrade to the latest code-push.
That works for me on stuck of ListView (rn 0.43, Android)

@fokoz
Copy link
Author

fokoz commented May 21, 2017

@flyskywhy The issue I've seen is on iOS, what about iOS of your project ? Does it stop spinning when out-in app ?

@flyskywhy
Copy link
Contributor

@smartdevth , sorry, I tested my APP again, code-push has no relationship. In my Android case, patch like this

sed -i "s/Platform.OS === 'ios'/Platform.OS !== 'web'/" node_modules/rn-viewpager/viewpager/ViewPager.js

actually solved my stuck problem, maybe this patch's root cause is ViewPagerAndroid ref to #13463 , and there is no stuck problem in my iOS project.

@fokoz
Copy link
Author

fokoz commented Jun 5, 2017

Any update on android?
Does anybody find this weird thing like me ?

@fokoz fokoz changed the title [RefreshControl] broken after re-enter app [iOS][RefreshControl] broken after re-enter app Jun 5, 2017
@hramos
Copy link
Contributor

hramos commented Aug 16, 2017

Hi there! This issue is being closed because it has been inactive for a while. Maybe the issue has been fixed in a recent release, or perhaps it is not affecting a lot of people. Either way, we're automatically closing issues after a period of inactivity. Please do not take it personally!

If you think this issue should definitely remain open, please let us know. The following information is helpful when it comes to determining if the issue should be re-opened:

  • Does the issue still reproduce on the latest release candidate? Post a comment with the version you tested.
  • If so, is there any information missing from the bug report? Post a comment with all the information required by the issue template.
  • Is there a pull request that addresses this issue? Post a comment with the PR number so we can follow up.

If you would like to work on a patch to fix the issue, contributions are very welcome! Read through the contribution guide, and feel free to hop into #react-native if you need help planning your contribution.

@hramos hramos added the Icebox label Aug 16, 2017
@hramos hramos closed this as completed Aug 16, 2017
@facebook facebook locked as resolved and limited conversation to collaborators Aug 16, 2018
@react-native-bot react-native-bot added the Resolution: Locked This issue was locked by the bot. label Aug 16, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Resolution: Locked This issue was locked by the bot.
Projects
None yet
Development

No branches or pull requests

4 participants