While testing, found some response does not parse correctly, even though there is a proper response. It occurs about 1 in every 3 to 4 attempts.
The causing issue is that HttpURLConnection passes the normal response in ErrorStream not in InputStream some reason. I assumed that some character set issue but not sure the causing issue because we uses same structure on every request/response. We get ErrorStream data if InputStream returns nothing for now.
While testing, found some response does not parse correctly, even though there is a proper response. It occurs about 1 in every 3 to 4 attempts.
The causing issue is that
HttpURLConnection
passes the normal response in ErrorStream not in InputStream some reason. I assumed that some character set issue but not sure the causing issue because we uses same structure on every request/response. We get ErrorStream data if InputStream returns nothing for now.Close #226