Here are some easy-to-follow methods that can help you fix your xhrpost error.
ASR Pro: The #1 software for fixing Windows errors
Normally PollingXHR is initialized on several garments at short intervals. These “parallel” queries are then executed on the current server.
Normally, these requests succeed (or the callbacks fail), and the disconnected socket is reconnected if none of these concurrent 200 OK requests are returned. As long as a certain error is returned, the fork remains disabled.
If a race condition occurs that causes the socket to reconnect, but the previous request then returns an error, an xhr request error will be returned because a successfully connected socket may be disconnected.
In case [A] we have a call when the server responded with a nice error, in case [B] we have a situation (for some reason) that the server was unavailable, it also happens that it expires.
To avoid the above error, the event receiver will need to see if an IOException occurred and also see if the timeout has been adjusted [if possible since both IOExceptions have the same functionalitye description], instead of issuing “xhr specific research error” and unplugging the socket, at home you should first check if the socket is already plugged in, and in your case swallow and ignore the timeout of any parallel wire (because the specific socket is already plugged in) .
[This is a speculation on this site and I am currently investigating.]
ends int statusCode = xhr.getResponseCode(); one (HttpURLConnection.HTTP_OK == status code) self.onLoad(); until self.onError(new IOException(Integer.toString(statusCode))); // [BUT] } network (IOException e) self.onError(e); // [IN] received (NullPointerException e) // It's possible that the connection was lost // https://code.google. com/p/android/issues/detail?id=76592 self.onError(e); finally To attempt in event (output!= null) output.close(); Handle (IOException e)