Exceptions on Android which look to occur from the HTTP component

[enchev]

From @maknz on August 16, 2015 23:23

I really have no idea on this one. I can't seem to figure out where it's coming from or what code is causing this. Anyone seen this before or know the likely culprit?

W/System.err( 8208): java.io.IOException: BufferedInputStream is closed
W/System.err( 8208):    at java.io.BufferedInputStream.streamClosed(BufferedInputStream.java:125)
W/System.err( 8208):    at java.io.BufferedInputStream.read(BufferedInputStream.java:265)
W/System.err( 8208):    at com.tns.Async$Http$RequestResult.readResponseStream(Async.java:168)
W/System.err( 8208):    at com.tns.Async$Http$HttpRequestTask.doInBackground(Async.java:295)
W/System.err( 8208):    at com.tns.Async$Http$HttpRequestTask.doInBackground(Async.java:245)
W/System.err( 8208):    at android.os.AsyncTask$2.call(AsyncTask.java:292)
W/System.err( 8208):    at java.util.concurrent.FutureTask.run(FutureTask.java:237)
W/System.err( 8208):    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1112)
W/System.err( 8208):    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:587)
W/System.err( 8208):    at java.lang.Thread.run(Thread.java:818)

Copied from original issue: NativeScript/NativeScript#598

[atanasovg]

Fixed with d99f169

[atanasovg]

(Re-open this, improperly closed)

This is most probably the same as #195. @maknz Could you please try the suggestion there?

[maknz]

We haven't seen this exception crop up in a while. I'll add that header in (because that'd be normal, anyway), and I'll post back if we see it crop up again.

[maknz]

We've seen this come back unfortunately :(. It seems to freak out when our server responds with 401 statuses. We don't get to deal with the response, it just blows it up before that.

We get this in the app:

and the original exception above in the console. Does that help at all?

[atanasovg]

This seems like a different error, a simple null-pointer exception. Will take a look.

[maknz]

Indeed, they seem unrelated, but they either both occur or neither do. We don't get the exception from the mobile app screen in the console, and we don't get the exception from the console in the app screen.

[atanasovg]

It turned to be a specific in the HttpUrlConnection implementation. See this SOF answer for more information. I've fixed this in the master and the fix will be available for the 1.5 release. Thanks for your input on this - it guided me into the right direction :)

[maknz]

I'm so glad to hear this! Thanks!

On Fri, Oct 30, 2015 at 5:39 AM, Georgi Atanasov notifications@github.com
wrote:

It turned to be a specific in the HttpUrlConnection implementation. See this SOF answer for more information. I've fixed this in the master and the fix will be available for the 1.5 release. Thanks for your input on this - it guided me into the right direction :)

Reply to this email directly or view it on GitHub:
#194 (comment)

[atanasovg]

Fixed with b12ae55 & 337fc78