Conversations can't receive msg or delete old fp.

[Sur3]

I switched to a new phone and now my conversations is unable to receive encrypted messages from lurch, I can send encrypted messages to lurch and they will be received, but I cant read messages from lurch; I says: "was not encrypted for this conversation".
Also it shows two different fp for the remote deviece, how do I delete the old fp?

[gkdr]

"was not encrypted for this conversation".

So that's what Conversations says? Is the new device on the device list when you look at it in lurch?

Also it shows two different fp for the remote deviece, how do I delete the old fp?

Again, this is what Conversations does? I think it keeps inactive devices for a while and then removes it later. Not sure if you can force the removal. I'm not a Conversations user so I can't help you there, sorry.

[Sur3]

No it's lurch that shows two different fp for the remote end, the question is how do I remove the old fp from lurch?
I just tested again and now I can send messages, seems lurch finally synchronized, but it should have done this directly when receiving messages..

[gkdr]

No it's lurch that shows two different fp for the remote end

This plugin just shows what's on the OMEMO devicelist, held by the server in a PEP node. Your old device probably still exists, and Conversations might not even do anything if you properly uninstall it. In any case, I think everything is working as expected. I don't know if you can remove devices from Conversations, but with lurch you can type /lurch remove id <ID> in any XMPP conversation window.

I just tested again and now I can send messages, seems lurch finally synchronized, but it should have done this directly when receiving messages..

This is unrelated to receiving messages. Messages are only encrypted for devices which are on the devicelist. In theory, any change (like adding a new device) should trigger an update for all subscribed devices, and every time the account connects the whole devicelist is received too. I can't tell at which part this procedure failed. Might be server code, the libpurple PEP implementation, or this plugin (though it's all the same code and I'm pretty sure it should work always or never).