Contact client type & keys not updated after client switch about chatsecureandroid HOT 3 OPEN

I don't quite understand the issue here. It sounds like you mean you are using a [email protected] account in both Adium and Gibberbot, and when a different app becomes active, Gibberbot didn't recognize it should use a different OTR key?

from chatsecureandroid.

Yes, I unfortunately found this one a bit difficult to explain in the initial write-up :) - but yes, your description is more or less what I'm describing.

It is linked to the concept of storing multiple keys for a contact - as that contact certainly may communicate via a desktop client as well as a mobile client like Gibberbot. I tested this case with n8fr8 this weekend as I switched from Adium to Gibberbot, and it was definitely a bumpy ride and took a lot of manual 'stop encrypted chat' or 'key regen' to get back to a normalized conversation.

from chatsecureandroid.

has this been solved on any of the desktop OTR clients? Or is Gibberbot performing worse than others? From my experience, the only way to get reliable OTR across multiple clients simultaneously is to use the exact same key in all running clients.

from chatsecureandroid.