-
Notifications
You must be signed in to change notification settings - Fork 189
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
Server is killed on iOS seemingly randomly and inconsistently #83
Comments
raymondjacobson
changed the title
Server is killed on iOS seemingly randomly, but inconsistently
Server is killed on iOS seemingly randomly and inconsistently
Feb 6, 2020
@raymondjacobson Did you ever find any workarounds or solutions to this problem? |
This issue appears to be related and it suggests a solution: httpswift/swifter#96 |
smellman
pushed a commit
to smellman/react-native-static-server
that referenced
this issue
Sep 25, 2024
…s, Lighttpd 1.4.73, a tiny correction in README
smellman
pushed a commit
to smellman/react-native-static-server
that referenced
this issue
Sep 25, 2024
smellman
pushed a commit
to smellman/react-native-static-server
that referenced
this issue
Sep 25, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi -- I'm using this project in a production application and observing a bizarre behavior where the server seems to randomly get killed by iOS. It's incredibly inconsistent (sometimes on first load, sometimes after app is backgrounded for a while, sometimes in the foreground) and I've been able to go many hours in a session (foreground, background, etc.) without this happening too.
Has anyone experienced anything similar or have any ideas on how to diagnose?
I've added a 500ms interval that pings the server and restarts it is it's down (this doesn't work). Maybe the OS is killing the interval as well? I've also added checks on app-to-foreground on server health and tried restarting, but those also don't seem to work either.
Thank you so much!
The text was updated successfully, but these errors were encountered: