Unexpected device message "DC on multiple devices that cannot decrypt each other's outgoing messages"

[lk108]

• Operating System (Linux/Mac/Windows/iOS/Android): Linux
• Core Version: 2.43.0 and 2.46.0
• Client Version: DeltaTouch 2.43.1 and dev version with core 2.46.0

On an otherwise working multi device setup, I got the device message It seems you are using Delta Chat on multiple devices that cannot decrypt each other's outgoing messages. To fix this, on the older device use "Settings / Add Second Device" and follow the instructions on a device running core 2.43.0.

As I only noticed the device message later, I'm not sure what exactly triggered it. Around that time, I tested chat descriptions with DeltaTouch on a device running core 2.46.0. For that, I created groups, deleted groups, added members and changed chat descriptions. According to timestamps, I may have changed a group description at the time the message was received, but it may also have been something in a group that I deleted.

[adbenitez]

I have similar setup: desktop 2.43.0 android 2.46.0

I removed a relay in desktop and got that weird message in android, if I go to relays in android the relay was not removed so this confirms it was the sync message

[Hocuri]

@adbenitez or @lk108 do you have a log?

[lk108]

@adbenitez or @lk108 do you have a log?

Unfortunately not

[link2xt]

This means crate::decrypt::decrypt failed somehow.
There should be a warning printed here:

core/src/mimeparser.rs

Line 435 in d1f1633

warn!(context, "decryption failed: {:#}", err);

Securejoin v3 was introduced in 2.45.0 and changed some code around decryption, but since the error was printed in 2.43.0, it cannot be directly related.

[link2xt]

If this cannot be reproduced, we can add error to this message by storing it in decrypting_failed instead of boolean, and close the issue.

[lk108]

I restored a backup from a few days ago on the 2.43 device, but the "cannot decrypt" message did not appear

[adbenitez]

Securejoin v3 was introduced in 2.45.0 and changed some code around decryption, but since the error was printed in 2.43.0, it cannot be directly related.

for me the error appeared in 2.46.0, not in 2.43.0, 2.43.0 was the one creating the sync message that somehow was seen as problematic by 2.46.0

[link2xt]

If this cannot be reproduced, we can add error to this message by storing it in decrypting_failed instead of boolean, and close the issue.

Made a PR for this: #8047

[link2xt]

Securejoin v3 was introduced in 2.45.0 and changed some code around decryption, but since the error was printed in 2.43.0, it cannot be directly related.

for me the error appeared in 2.46.0, not in 2.43.0, 2.43.0 was the one creating the sync message that somehow was seen as problematic by 2.46.0

What I meant is that decryption failure was not introduced after 2.43.0 with some decryption code change, but is either a problem with encryption or some older problem that existed at least since 2.43.0.