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

"JS has only made partial progress to catch up to UIKit" in UIExplorer app #731

Closed
marshallbrekka opened this issue Apr 7, 2015 · 1 comment
Labels
Resolution: Locked This issue was locked by the bot.

Comments

@marshallbrekka
Copy link

When clicking/tapping rapidly on the back button in the NavigatorIOS example it triggers the mentioned error message.
The comment where that error originates from indicates its probably a bug with the JS, but doesn't indicate what the solution would be.

// We can actually recover from this situation, but it would be nice to know
// when this error happens. This simply means that JS hasn't caught up to a
// back navigation before progressing. It's likely a bug in the JS code that
// catches up/schedules navigations.
if (!(jsGettingAhead ||
jsCatchingUp ||
jsMakingNoProgressButNeedsToCatchUp ||
jsMakingNoProgressAndDoesntNeedTo)) {
RCTLogError(@"JS has only made partial progress to catch up to UIKit");

For what its worth the same bug is present in this app as well https://github.com/iSimar/HackerNews-React-Native

react_native_navigator_bug

@corymsmith
Copy link

This is a duplicate of #65

@facebook facebook locked as resolved and limited conversation to collaborators May 29, 2018
@react-native-bot react-native-bot added the Resolution: Locked This issue was locked by the bot. label Jul 23, 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