Is 4 the latest build? Try to update, retest...

I should have mentioned, the bug persists even in 7.1(7), which is the latest.

The version which was released around 20 minutes ago?

Also, please keep in mind that the issue you are reporting is with other clients sending messages to Siskin which is unable to decode.

What clients are being used for sending those messages? Are you using other clients on the same account? If you are using other clients, is your SiskinIM-OMEMO key enabled?

Yes, both the latest version ( the one from half an hour ago ) and the one before it have this issue.

We have a MUC hosted on a Prosody server.

I can send messages to private convos without issues.

My friends are both using Blabber.im clients.

I use BeagleIM as my other client, and it works without issue. Of note is that messages I send from Beagle are readable in siskin and vice versa.

I have my keys trusted.

SiskinIM and BeagleIM both are using the same library for OMEMO encryption which was tested against Monal and Conversations and was working fine. Actually, after changes in version 7.1 (b1-b7), it is even more stable than it was before.

I cannot comment on Blabber.IM as I'm not using it (no Android device laying around), but you've mentioned that you are not seeing their avatars. That would mean, that either their presence is not forwarded properly or there is some issue with iq forwarding between Blabber.IM clients and your clients (iq forwarding done by MUC in Prosody).

Hm is there any chance I might find something in the app logs?

Update: looked into the logs using console on my mac, nothing useful... I'll try to see if prosody is logging anything

Hi,

a friend from me with the following device:

• Siskin Version: 7.1
• Branch: Stable (from 14.02.2022)
• iOS version 14.4
• iPhone 7

has the same problem. Sending in Mucs with Omemo is all fine, but when they receiving messages with Omemo, he can´t read it. We have tested with Dino 0.3 and Conversations 2.9.10. The problem is since update to the new version. Anyone a idea?

They would be update in first step the IOS Version and give you an update, if they help.

Yeah, I've tried changing server's ( using the tigase xmpp server also doesn't seem to solve the issue ), it's still there...

@jtmaston What you have actually changed? used new account? or created a new room on Tigase XMPP Server MUC?

@hantu85. a little more information from my side. We used a Ejabberd 21.12 and i have create a new muc with my friend, but there is the same problem. He can send with omemo, but received can't read "message decryption failed".

Update: The change to IOS Version 15.3 are not solved the problem.

Unfortunately, I cannot fix this issue as there were almost no changes in message decoding and none of the changes can be pinpointed as the source of this problem.

I've added additional debug information (error code) which will be displayed to the user if decoding will fail. This should allow us to know what actually is failing and then apply a fix.

This change will be part of the first build of SiskinIM 7.w which should be released soon.

Thanks, I'll have a look when that drops. Sadly it's been pretty hectic on my end so I haven't had more time to test.

When I deployed tigase I made a whole new user, new MUC, had a friend create a user and join the MUC from his client and the issue was still there.

I'll come back with more testing soon

Just another one … #sry

• Server: Prosody 0.11 nightly build 143 (2022-01-24, 458c5f8d5d3e)
• Clients/Devices:
  • 10 sending: Conversations (multiple current versions), Gajim (1.1.3)
  • 2 receiving: Siskin 7.1
• Issue: receiving devices can't decrypt OMEMO messages from sending devices
  • FYI: sending devices can decrypt OMEMO messages from receiving devices can

.oO(Has someone maybe verified that issue doesn't exists with BeagleIM …)

KR

Could someone check if the issue happens (recipient not able to decrypt) when the sender is in the room or only when the sender of the encrypted message is not in the room when the recipient actually received this message?

Could someone check if the issue happens (recipient not able to decrypt) when the sender is in the room or only when the sender of the encrypted message is not in the room when the recipient actually received this message?

@hantu85 I had the situation (while writing the last comment) that all Siskin users (and me, Conversations + writing test messages ;-)) were in the room.

As said in the support channel, my users see the same. Conversations users are always online, as usual.

ejabberd almost HEAD

Did anyone check when this error message occurs, if on the list of occupants in the room in SiskinIM senders for which decryption of messages fails are visible as available?

Newly released beta build 7.2-b1 (on TestFlight), contains a fix on recently reported issue with participant status presentation in MUC rooms. This may be cause of this issue as well.

If possible, please try new build and check if it solved the issue. If not, please report error code presented in the error message, which will help us fix the issue.

@hantu85 I got positve feedback (and self-experience with Conversations) from 2 iOS users that the recent TestFlight version is working (again)! #thanks!

So can you please publish the TestFlight version as the current/stable release.(?)

@jtmaston Is the problem fixed, now with 7.2? ?? Thanks + KR!

@jtmaston Is the problem fixed, now with 7.2? ??

Thanks + KR!

Sadly, I have no means to test it now. Xmpp proved to be too unreliable for our application so we switched to something else.