App resume and HTTP error


#1

Hello there I am facing this situation every once in a while (and more so in Android compared to iOS)

When the app is “resuming” from the background, typically after the phone is locked, every once in a while my first HTTP request fails - returns null.
Subsequent requests work.

My suspicion is that it is something do with network not being ‘ready’ and happens randomly - but when you resume from the background, there is no deviceReady callback - that only happens when the app first starts.

Has anyone experienced this and if so, whats a good way to avoid this?

thanks


#2

We see the same issue. Did you ever resolve this?


#3

No, I got busy with other stuff, but this is still something I can’t quite put my finger on. Have you managed to zero in on exactly what conditions this happens?


#4

No. I can say that if we delay the requests that are fired on resume things are more stable. But it’s definitely not a reliable workaround.