v.2.2.4

• Removed unnecessary code in the TweetNaClFast implementation
• Updated the Java-WebSocket library to 1.5.1 as the current version 1.4.0 has a known critical vulnerablity.

v2.2.3

Fixed LazySodium causing a crash on Android devices by swapping it out for TweetNaCl

v2.2.2

Fixed an issue where some private encrypted messages were not decrypted accurately by swapping our implementation of SecretBoxOpener for one provided by Lazy Sodium

v2.2.1

Changed PusherOptions setForceTLS and isForceTLS to setUseTLS and isUseTLS to align with the other client SDKs.

v.2.2.0

Changed PusherOptions setEncrypted and isEncrypted to setForceTLS and isForceTLS to reduce confusion between this option and private encrypted channels.

v2.1.1

• Fix a case where multiple websocket connections could be opened at once if reconnection was triggered by an activity timeout.

v2.1.0

Add private encrypted channels.

v2.0.2

• Make a no-op state change non-fatal, allowing transitions to/from the same state

v2.0.1

• Forward channel_data returned by the auth endpoint when subscribing to private channels

v2.0.0

• The onEvent handler now gets called with one parameter, called the PusherEvent. This PusherEvent has all the same information available as was available before with the 3 parameters, but now is accessible by calling getChannelName(), getData() or getEventName() on the PusherEvent object you receive. In addition, for presence channel client events, you can now retrieve an authenticated User ID by calling getUserId() on the PusherEvent object. To read more on Authenticated users, see the README or our docs here.
• Update Java sourceCompatibility and targetCompatibility to 1.8.
• Fix an issue where the reconnect logic would not be reset after connect() is called again.
• Depend on org.java-websocket:Java-WebSocket:1.4.0 instead of com.pusher:java-websocket:1.4.1.