ably-java
ably-java copied to clipboard
ably
Java, Android, Clojure and Scala client library SDK for Ably realtime messaging service
Hey @paddybyers, during reading the Java's realtime Presence implementation I spotted two minor things I think either differ from the spec or possibly may be a bug. * there's no...
See https://github.com/ably/ably-java/blob/master/lib/src/main/java/io/ably/lib/realtime/Channel.java#L494-L497 The publish method can raise an `AblyException`, but also has a [`completionListener`](https://github.com/ably/ably-java/blob/master/lib/src/main/java/io/ably/lib/realtime/CompletionListener.java) which handles success & failure conditions. Now if you look at https://goo.gl/Hc0yqK, you can see that...
A customer has asked how they can call `client.auth.authorize` in a non-blocking way. Currently, in the Java lib I believe this is only possible with a new thread. Should we...
Client lib version: 0.8.8 Customer has reported that during the following sequence, they fail to publish a message, and inspecting the logs, there is a `NullPointerException`. * Connect to ably...
https://github.com/ably/docs/pull/203 ┆Issue is synchronized with this [Jira Task](https://ably.atlassian.net/browse/ECO-4220) by [Unito](https://www.unito.io)
A realtime library instance gets into a state, after some combination of having lost (and regained) a network connection, and a failing `authCallback`, in which all transport events are discarded...
Repro: Use AuthCallback for Ably authentication Send 404 or invalid token Check logs Actual: In logs we see Auth service is tries ~30sec. The connection goes in disconnected state right...
Looking at https://github.com/ably/ably-java/blob/master/lib/src/main/java/io/ably/lib/transport/ConnectionManager.java, looks like currently if a transport dies, pending (unacked) messages are left in pendingMessages; they should be requeued (removed from pendingMessages and added to queuedMessages), to be...
Paddy said: That’s been an intermitted failure since the beginning of time. I looked at it once, and have no real idea why. If it happens 16th of the time...
RealtimeReauthTest has a 2s delay after doing a reauthorise. Without it the test fails with an unexpected exception. ConnectionManager.onAuthUpdated() tells the transport to close, so when the test immediately attempts...