Reported here.
This happens, when the OmemoManager was first created using OmemoManager.getIntanceFor(Connection) before the user logged in. In that case, there are two new jid folders in the OMEMO store: "user@server.tld" and "user".
When the client than tries to get an instance of the OmemoManager via getInstanceFor after the user logged in, it gets an instance, that has no key material, so processBundle will throw an exception.
I suggest to either only create the OmemoManager after login, or keep one instance of the OmemoManager around as a local variable. Nevertheless, this must be fixed.
vanitasvitae
commented
6 years ago
Reported here. This happens, when the OmemoManager was first created using
OmemoManager.getIntanceFor(Connection)before the user logged in. In that case, there are two new jid folders in the OMEMO store: "user@server.tld" and "user".When the client than tries to get an instance of the OmemoManager via getInstanceFor after the user logged in, it gets an instance, that has no key material, so processBundle will throw an exception.
I suggest to either only create the OmemoManager after login, or keep one instance of the OmemoManager around as a local variable. Nevertheless, this must be fixed.