We are seeing truncation of the data member when a ProtocolMessage is encoded.
The problem has been confirmed on Android 4.4.2 with the ably-java 0.8.8 library, which uses msgpack-core 0.8.11.
The problem is not seen on ably-java 0.8.7 (using msgpack-core 0.8.2).
The following platforms seem to have no issue:
Any Oracle JRE
Android 5.0.1, 6.0, 7.0.
The suspicion is a incompatibility between the msgpack lib and the version of java.nio.charset.CharsetEncoderICU in earlier Android versions. There have been several issues with msgpack, and there are still open issues on 0.8.11: msgpack/msgpack-java#405.
Plan is to:
-
narrow down the specific string or struct that causes the issue so we can file an issue with msgpack;
-
in the ably-java lib, force use of the JSON encoding on android versions < 5.0.
We are seeing truncation of the
datamember when aProtocolMessageis encoded.The problem has been confirmed on Android 4.4.2 with the ably-java 0.8.8 library, which uses msgpack-core 0.8.11.
The problem is not seen on ably-java 0.8.7 (using msgpack-core 0.8.2).
The following platforms seem to have no issue:
Any Oracle JRE
Android 5.0.1, 6.0, 7.0.
The suspicion is a incompatibility between the msgpack lib and the version of
java.nio.charset.CharsetEncoderICUin earlier Android versions. There have been several issues with msgpack, and there are still open issues on 0.8.11: msgpack/msgpack-java#405.Plan is to:
narrow down the specific string or struct that causes the issue so we can file an issue with msgpack;
in the ably-java lib, force use of the JSON encoding on android versions < 5.0.