Any attempt to open the debugger throws a NetworkOnMainThread exception about haul HOT 14 CLOSED

Another think I'm noticing is that the debugger continually tries to load on 10.0.2.2 (which I indicated above), I have to manually change the URL to localhost

from haul.

Does your app have the Draw over other apps permission?

from haul.

Yep

from haul.

Can you double check? Because according to the error message, it does not.

from haul.

Ah, sorry. I posted the wrong stack trace, still had that on my clipboard from earlier. I've left the office for the day but tomorrow I can get the correct one in here

from haul.

We were experiencing similar issues earlier today, I'll debug them on device in the morning.

from haul.

Here's the crash:

E/AndroidRuntime: FATAL EXCEPTION: main
                  Process: com.hubspot.android.debug, PID: 3154
                  android.os.NetworkOnMainThreadException
                      at android.os.StrictMode$AndroidBlockGuardPolicy.onNetwork(StrictMode.java:1303)
                      at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:111)
                      at java.net.SocketOutputStream.write(SocketOutputStream.java:157)
                      at okio.Okio$1.write(Okio.java:78)
                      at okio.AsyncTimeout$1.write(AsyncTimeout.java:180)
                      at okio.RealBufferedSink.emit(RealBufferedSink.java:178)
                      at okhttp3.internal.ws.WebSocketWriter.writeControlFrameSynchronized(WebSocketWriter.java:152)
                      at okhttp3.internal.ws.WebSocketWriter.writeClose(WebSocketWriter.java:111)
                      at okhttp3.internal.ws.RealWebSocket.close(RealWebSocket.java:168)
                      at com.facebook.react.devsupport.JSDebuggerWebSocketClient.closeQuietly(JSDebuggerWebSocketClient.java:144)
                      at com.facebook.react.devsupport.WebsocketJavaScriptExecutor$3.run(WebsocketJavaScriptExecutor.java:146)
                      at android.os.Handler.handleCallback(Handler.java:751)
                      at android.os.Handler.dispatchMessage(Handler.java:95)
                      at android.os.Looper.loop(Looper.java:154)
                      at android.app.ActivityThread.main(ActivityThread.java:6119)
                      at java.lang.reflect.Method.invoke(Native Method)
                      at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:886)
                      at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:776)

It seems like there may be more networking issues as well. Seeing hundreds of instances of this log message in the application logs:

W/OkHttp: A connection to http://10.0.2.2:8081/ was leaked. Did you forget to close a response body?

from haul.

I've done some tests and managed to reproduce this crash. So far it seems to be happening only when debugger is being opened for the first time. Having it opened from previous session and running the app seems to work fine.

Looking into it now.

from haul.

That has been already fixed (see open PR).

from haul.

Oops, thanks @grabbou, didn't see the linked PR

from haul.

Looks to be more networking issues at play. Upgraded to 0.3.0 and now I see a message CANNOT TRANSLATE guest DNS ip logged to the device console (not the application logs) every 4 seconds or so. With this, I can't actually run any react native code. The app starts up fine (reactContext is non null, any statements in my index.android.js file are executed) but trying to load a component fails silently. See description of the problem here: http://stackoverflow.com/questions/43229683/react-native-component-not-mounting

from haul.

^^ after a little more playing that all looks to be related more to react-native than haul, can close this in lieu of an issue over there: facebook/react-native#13340

from haul.

whoops. may have closed this prematurely. was this where the issue of opening the debugger causing a NetworkOnMainThread exception was being tracked? that's still an issue in 0.5.0

from haul.

As per your previous reply, this is an issue in React Native and not haul. So there's not much point of keeping this issue open. It's not actionable for us.

from haul.