-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
setTimeout handler is not called #4372
Labels
Comments
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. |
The issue has been closed for inactivity. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Issue Description
A piece of our network logic involves a delay to collect WS messages for batch sends. The relevant code looks like this:
Most of the time, this works fine. However, sometimes the timeout handler (
sendCurrentBatch
) is never invoked. Typically, this happens when transitioning between different screens; I’m not sure which project this bug should be filed under: RN or RNN? I have a vague suspicion that it might be something like facebook/react-native#22089 (“Timers do not run if specified before App mounts”), compounded by the fact that (if I understand correctly) RNN, on some level, creates more than one “app”. I do not know the details.But it seems very…wrong…that a function like
setTimeout
can somehow stop working in the middle of a running application.Environment
The text was updated successfully, but these errors were encountered: