Nathan Freitas

I will work on prioritizing it. We've gotten v14 mostly stable and worked through the network and OTR bugs. I can try to get it in for next weeks release....

Hmm... actually there might be. Let me look into that. In the meantime, you can install v13, run keysync, then upgrade to the latest v14 build, as an option.

This is happening for others, as well, and we will have a fix in the next update this week.

One question - do you or any of these contacts use any other OTR chat programs like Pidgin or Adium?

We've push an update to Google Play, or you can grab the latest release here: https://guardianproject.info/releases/ChatSecure-v14.0.3.apk

Pushing another update today. I think the problem relates to using the wrong JID. If we are [email protected]/blah but the server actually sets us to [email protected]/blah123 we were not getting...

We've pushed changes that affect this bug, and have released 14.0.4 official as well: https://guardianproject.info/releases/ChatSecure-v14.0.4.apk

The keystore file corruption is not related to the DB closing. The fact that you can establish an OTR session at means your keystore is intact. The OTR issues you...

Glad you can repro, hc. I think a few issues are being conflated here though. v13 and existing v14 code definitely has issue with OTR and XMPP resources that could...

I do think, hc, that what you reproduced relates to the issue I have seen of this problem mostly happening on first-time use/setup. Once it stops happening, then it is...