When I import a keystore from KeySync it confirms a succesful sync yet my fingerpint hasn't changed

[FelixAkk]

I really love ChatSecure, but this is the last part that prevents us for properly using OTR is having consistent fingerprints across our devices. Without this it's driving me and my friends nuts, with changing fingerprints breaking encryption all the time. In my case I'm trying to import the Adium fingerprint to ChatSecure on Android 4.3 using the KeySync command line tool (the GUI doesn't work for any of us, see: https://dev.guardianproject.info/issues/2894).

Right now exporting to the keystore file and activating the import on ChatSecure all works. But after it gives the small success notification, the client and everyone else still reports I have the same fingerprint.

I really hope this get's fixed soon!

[comzeradd]

This is part of the 14.2 Milestone but it doesn't seem resolved. Changelog also mentions that keysync was re-implemented, but with this bug it's actually only the UI in place.

Any plans to fix this soon. It's really important for OTR usability.

[kocmo]

Problem still present in version 14.2.3