ably-java
ably-java copied to clipboard
Java, Android, Clojure and Scala client library SDK for Ably realtime messaging service
withakay points out that ably-java uses 91200 for channel attach timed out, which isn't in errors.json. Ably-js uses 90007 ("channel operation failed (no response from server)") for that ┆Issue is...
There's a request to be able to get detailed logs, but excluding actual message payloads. Currently, `VERBOSE` logs contain a lot of detail necessary for debugging, but also message payloads....
as defined in https://github.com/ably/docs/pull/182/files ┆Issue is synchronized with this [Jira Task](https://ably.atlassian.net/browse/ECO-4263) by [Unito](https://www.unito.io)
I set the test suite to temporary ignore it. See https://github.com/ably/ably-java/commit/cd89c8f405f27fb21f5669849200fd353d825a39 Failure happens usually on this line https://github.com/ably/ably-java/blob/66f639876fbbd43d020dd82e059fc7a33d22c4f3/lib/src/test/java/io/ably/lib/test/rest/RestChannelHistoryTest.java#L327 sometimes with text, sometimes with binary. Sometimes in java, and sometimes in...
See https://github.com/ably/docs/pull/446 ┆Issue is synchronized with this [Jira Task](https://ably.atlassian.net/browse/ECO-4260) by [Unito](https://www.unito.io)
https://github.com/ably/ably-java/blob/2af72fb88e0d5e0b47820c1c1cab6a2235f5df73/lib/src/main/java/io/ably/lib/realtime/Channel.java#L747-L751 This was correct for 0.8, and is still correct for `failed` or `suspended`, but in the 1.0 spec, publishing while `detached` should trigger an implicit attach (for 1.0 spec...
This is a spin off of https://github.com/ably/ably-java/issues/364 ┆Issue is synchronized with this [Jira Task](https://ably.atlassian.net/browse/ECO-4255) by [Unito](https://www.unito.io)
Like we have in iOS. ┆Issue is synchronized with this [Jira Task](https://ably.atlassian.net/browse/ECO-4254) by [Unito](https://www.unito.io)
See https://github.com/ably/ably-java/blob/159018c30b3ef813a9d3ca3c6bc82f51aacbbc68/lib/src/main/java/io/ably/lib/realtime/Presence.java#L901-L912 and https://github.com/ably/ably-dotnet/pull/157#discussion_r149350461 If we receive a presence message from Ably that is malformed, then the client can no longer guarantee integrity of that connection, but more specifically possibly...
See https://github.com/ably/ably-dotnet/pull/127#issuecomment-327613915 Is it perhaps idiomatic to have a shared static logger between all instances of a library? It seems odd that you could set the log level in one...