Android 5.0 Lollipop wss stopped working

[szczepaan]

Hey,

below code worked for Android 4.x.x (also Kitkat), and stopped working on Lollipop

SSLContext sslContext = null;
        try {
            sslContext = SSLContext.getInstance("TLS");
            sslContext.init(null, null, null); // will use java's default key and trust store which is sufficient unless you deal with self-signed certificates
        } catch (NoSuchAlgorithmException e) {
            e.printStackTrace();
        } catch (KeyManagementException e) {
            e.printStackTrace();
        }
        mWebSocketClient.setWebSocketFactory(new DefaultSSLWebSocketClientFactory(sslContext));

mWebSocketClient.connect();

I dont get any error, it just doesnt connect to wss server, onOpen() is never called :/

Please help

[johnnyzen]

We are using lollipop and not getting this issue.. what device are you using?

[szczepaan]

Are You using the same code as mine and WSS ?

mWebSocketClient = new WebSocketClient(uri, new Draft_17()) 

LG Nexus 5

[khk624]

I have same issue here. It only has a problem with Lollipop.
My code is almost same with @szczepaan, but I've used X509TrustManager for sslContext.init().

Tested on Nexus 7 (Android 5.0)

[aeirola]

I'm experiencing the same problems as above. Checking the debugger it seems as if the reader thread is stuck in the SSLSocketChannel2.unwrap() loop with sslEngine being an instance of OpenSSLEngineImpl. The sslEngine.unwrap() call constantly returns with bytesConsumed=0, bytesProduced=0 and handshakeStatus=NEED_UNWRAP.

Need to investigate further what this is about...

EDIT: Add some links

[aeirola]

So apparently NativeCrypto.SSL_do_handshake_bio return 0 in the code, which according to the documentation means

"The TLS/SSL handshake was not successful but was shut down controlled and by the specifications of the TLS/SSL protocol. Call SSL_get_error() with the return value ret to find out the reason."

Without access to the context, and calling SSL_get_error, it'll be too hard to continue debugging.

I guess I'll just use some other websocket library, like AndroidAsync...

[andredigenova]

I had this issue and rewrote SSLSocketChannel2 to use SSLEngine in the way I saw several other projects use it. The code seems to work for me but it definitely needs more testing. I have only used it as a WSS client, but it should behave the same for servers.

https://github.com/andrepew/Java-WebSocket/tree/1.3.0-Android-SSL-Fix

[earlymarket-oc]

I can confirm, on Nexus 5 with Lollipop WSS is not working at all.

[porkyhead]

Can confirm that the issue exists on Nexus 9 Lollipop.

Andrepew's solution is working on Lollipop but crashes on Kitkat (and maybe even older Android versions), so there is no single solution for using websocket SSL on Android in general :(

[juanjo75es]

Couldn't it be that Lollipop has a different list of supported CA's and now your root certificate is not accepted by your client?

[phu-tang]

I have a same problem with Nexus 5 (5.0.1) but seem work on 5.1. do you have any idea to fix it?

[Jullekungfu]

@andrepew I had the exact same issue as described above, your provided fix solved everything!
Thanks! :D

[sristi]

@andrepew I confirm that I had tested your version of java_websocket.jar with WSS protocol on Android 4.1.2 to 6.0 emulators and devices from major android device vendors. Moreover, I had tried wss connections on older version of device/emulators having android 4.0.3 and previous ones. But wss did not work for them and I simply make a fallback to ws protocol to those devices. Hats off to your work !