android.os.NetworkOnMainThreadException about cordova-plugin-chrome-apps-sockets-tcp HOT 4 CLOSED

Possibly related: on a Nexus 5X with Android M, API level 24, I'm seeing messages like
W/PluginManager: THREAD WARNING: exec() call to ChromeSocketsTcp.connect blocked the main thread for 458ms. Plugin should use CordovaInterface.getThreadPool().

458 ms seems like a long time. Maybe this is a blocking API that shouldn't be used on this thread?

from cordova-plugin-chrome-apps-sockets-tcp.

I have the same problem on Android 4.1.2

E/PluginManager(10586): Uncaught exception from plugin
E/PluginManager(10586): android.os.NetworkOnMainThreadException
E/PluginManager(10586):     at android.os.StrictMode$AndroidBlockGuardPolicy.onNetwork(StrictMode.java:1117)
E/PluginManager(10586):     at libcore.io.BlockGuardOs.connect(BlockGuardOs.java:84)
E/PluginManager(10586):     at libcore.io.IoBridge.connectErrno(IoBridge.java:127)
....

The older cordova-plugin-chrome-apps-socket works on android 4.1.2.
But that version of ChromeSocket.java wraps connect in a ConnectThread class. Was there a point of doing this different in the newer cordova-plugin-chrome-apps-sockets-tcp ?
Or is this just the 'new' android way, and there was no basis for keeping compatible with the older android versions?

from cordova-plugin-chrome-apps-sockets-tcp.

Certainly looks like .connect() should be run on a dedicated background thread.

from cordova-plugin-chrome-apps-sockets-tcp.

Published in v1.3.6

from cordova-plugin-chrome-apps-sockets-tcp.