Using Conversation simultanously on two device lead to error "OMEMO-Nachricht konnte nicht entschlüsselt werden"

[bitschieber-1]

Translated: "OMEMO-Message could not be decrypted"
one mobile with Android 8.1 (Conversation 2.11.3+free) the other with Android 11 (Conversation 2.10.10+free).
The mobile, where i send the last message, can decrypt the received message.

[licaon-kter]

So you've installed on device 1, logged in.

Then installed on device 2 and logged in.

Yes?

You send a message to a contact in 1:1 chat or to a private group?

[bitschieber-1]

Hello, message to contact 1:1 and yes, i installed first on android 8, logged in, sometime later got new device fairphone4 with android 11 where i installed and logged in. The device where i send the last message works fine. The other device receives with error message. Am 05.01.23 um 12:12 schrieb Licaon_Kter:

…

So you've installed on device 1, logged in. Then installed on device 2 and logged in. Yes? You send a message to a contact in 1:1 chat or to a private group? — Reply to this email directly, view it on GitHub <#4437 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A5C5YGSD7O5IJH7P7HCGLN3WQ2UDTANCNFSM6AAAAAATRZ7FI4>. You are receiving this because you authored the thread.Message ID: ***@***.***>

[licaon-kter]

Your contact uses which client?

Can you update 2.10.10 to 2.11.3 just in case too?

[bitschieber-1]

My Buddy says conversation ist Version 2.11.3+free von FDroid installiert. And he host a own server Prosody 0.11.2 auf einem Raspberry (Linux raspberrypi 5.10.103-v7+ #1529 SMP Tue Mar 8 12:21:37 GMT 2022 armv7l) On the fairphone4 no update is possible in fdroid, 2.10.10 is shown as the latest version Licaon_Kter ***@***.***> schrieb am Do., 5. Jan. 2023, 12:44:

…

Your contact uses which client? Can you update 2.10.10 to 2.11.3 just in case too? — Reply to this email directly, view it on GitHub <#4437 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A5C5YGRV4A6QCMJPWK63673WQ2XYRANCNFSM6AAAAAATRZ7FI4> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[licaon-kter]

On Fairphone 4, pull to update index in F-Droid, then update.

Does your contact see, in their appo 2 keys for you in Contact details?

[bitschieber-1]

Hello my contact see in his app one key for me in Contact details, but he can choose to which device he want to send to. somehow wired.  he actually installed profanity as commandline tool on the server for test, now i see 2 keys in his contact details. I updated conversation on fairphon4. the issue is for me actually not a real problem. i want to update the fairphone4 to /e/OS in the next days and when that is done i will stop using the second phone, so it is not urgend. Am 05.01.23 um 14:39 schrieb Licaon_Kter:

…

On Fairphone 4, pull to update index in F-Droid, then update. Does your contact see, in their appo 2 keys for you in Contact details? — Reply to this email directly, view it on GitHub <#4437 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A5C5YGSMRVFCW7ECCT4NLPTWQ3FJJANCNFSM6AAAAAATRZ7FI4>. You are receiving this because you authored the thread.Message ID: ***@***.***>

[licaon-kter]

@bitschieber-1 /e/os? Awful, try Divest or Calyx maybe :)

Odd that they see only one key, maybe it's a server issue? Their profanity see only one key for you too?

Did you ever verify QR codes between you and your contact?

[bitschieber-1]

Hello Licaon_Kter, thanks for the hint to alternatives to /e/os... i searched for other options on your hint and found additional iodéOS which sound interessting too, but very unsure which to choose now, need to do some research. To the conversation problem, maybe realy a server issue. Not sure if we verified OR Codes. The messages were shown as encrypted (green) with OMEMO (little lock under the messages). But i can do, i see him usally once a week. Am 05.01.23 um 18:28 schrieb Licaon_Kter:

…

@bitschieber-1 <https://github.com/bitschieber-1> /e/os? Awful, try Divest or Calyx maybe :) Odd that they see only one key, maybe it's a server issue? Their profanity see only one key for you too? Did you ever verify QR codes between you and your contact? — Reply to this email directly, view it on GitHub <#4437 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A5C5YGWY4OJHURFYAL2TOF3WQ4ADDANCNFSM6AAAAAATRZ7FI4>. You are receiving this because you were mentioned.Message ID: ***@***.***>

[licaon-kter]

@bitschieber-1 iode just barely published its source code last month, I would not bother.

Ok, lock means "encrypted" while shield means "verified".

You could try to send unencrypted messages too, from all the devices, to test, then enable omemo again and retry.

Another question, do you see 2 keys in YOUR clients on both devices? Accounts - your Account...how many fingerprints listed?

[bitschieber-1]

Under account i see 3 finger prints, first has heading "session restored"  and the two others with heading "other devices". This looks identical on both device. Am 05.01.23 um 19:52 schrieb Licaon_Kter:

…

@bitschieber-1 <https://github.com/bitschieber-1> iode just barely published its source code last month, I would not bother. Ok, lock means "encrypted" while shield means "verified". You could try to send unencrypted messages too, from all the devices, to test, then enable omemo again and retry. Another question, do you see 2 keys in YOUR clients on both devices? Accounts - Accounts...how many finger prints? — Reply to this email directly, view it on GitHub <#4437 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A5C5YGSCOCXY6UEKGFP2AODWQ4J6DANCNFSM6AAAAAATRZ7FI4>. You are receiving this because you were mentioned.Message ID: ***@***.***>