You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It appears to be specific messages only, but those messages can apparently still sometimes be successfully decrypted, but not other times.
Unclear whether the messages in question were published from ably-java or ably-cocoa, but it is one or the other. Also unclear whether the problem is limited to messages published by only one of those client libs, or both. So may be an ably-cocoa bug.
See internal channels for example of a raw message that sometimes can't be decrypted
The text was updated successfully, but these errors were encountered:
Sorry if that was unclear -- I just meant our internal company slack. It's a bug report from a customer, the message can't be made public for data privacy reasons.
Re a test case -- no, one does not exist now, once we figure out what happens well enough to write a test that consistently reproduces the issue we'll be most of the way towards solving it 🙂
@QuintinWillison is coordinating the response for this; liaise with him 🙂
Customer reports that encrypted messages are occasionally unable to be decrypted:
It appears to be specific messages only, but those messages can apparently still sometimes be successfully decrypted, but not other times.
Unclear whether the messages in question were published from ably-java or ably-cocoa, but it is one or the other. Also unclear whether the problem is limited to messages published by only one of those client libs, or both. So may be an ably-cocoa bug.
See internal channels for example of a raw message that sometimes can't be decrypted
The text was updated successfully, but these errors were encountered: