Issue with okhttp silent retry on connection failure

0
votes

We have some issue with okhttp retrying request. Most of our clients are receiving too much of this kind of exception according to our crash reporting logs.

enter image description here enter image description here

What they complain about is that data is uploaded to the server but mobile still shows as not uploaded. I have researched a bit and found that okHttp is retrying requests on connection failure and guess it is related to this topic. I can't create a case while debugging the app. I have tried to connect to 10.10.10.1, it is getting socket timeout, but it seems that okhttp doesn't retry this request. It just returns on this line if (!streamAllocation.hasMoreRoutes()) return false; (okhttp v3.12.1). I can't see any logs on retrying in logcat or stetho. How to reproduce this case? Should okHttp retry in this case? Will disabling retry help in this case?

Per this article https://medium.com/inloopx/okhttp-is-quietly-retrying-requests-is-your-api-ready-19489ef35ace

You will not get notified about these silent retries. The server can receive multiple requests even though you made only a single request.

1
androidtimeoutokhttp3

1 Answers

0
votes

I managed to replicate the case based on okhttp standard test. Here is the test https://gist.github.com/androideveloper/b411d9e90cb8ad430148a906890d0c90. It retries silently 2 times. Logs are available if logging interceptor is installed as a network interceptor.