OMEMO not supported by your contact

[shodanx2]

running ejabberd server version 20.01-1, no particular errors about that in log files

uwpx v0.40.1.0 on two clients

As shown in screenshot, it says OMEMO not supported by your contact.

[COM8]

Thanks for reporting!
Do I understand this correctly. You are running UWPX on two devices and it says "OMEMO not supported by your contact"?
If so, please could you have a look at all available devices and let me know if there are any and how they are called?

[COM8]

Any updates @shodanx2 ?

[shodanx2]

Hello
When I opened this issue, I had a rather different setup.
The ejabberd server was running off a single .pem file which had no set domain name

But one problem I found was that OMEMO was simply not enabled in the app.
In settings -> general -> chat -> OMEMO

I think that should be on by default, since you also have to enable it in the chat window

To try, I created to blank accounts and installed UWPX on two different PC.

I enabled set them up and enable OMEMO at both ends.

Unfortunately, this still does not work.

While setting things up, I noticed that deleting an account doesn't always work.
After application restart, the deleted accounts come back, the only way to really delete them was to uninstall and re-install the application.

Perhaps other settings are "sticky" like that ?

So here is what is happenning. I have two users, testuser2 and testuser3, I tried to make both send one another OMEMO messages.

Before I managed that, I sent a message from testuser2 to testuser3
Something went wrong, a second chat for testuser2 appeared on testuser3
And as I switched between the two, the message sent by testuser2 was repeated multiple times !?

After this, I enabled OMEMO encryption on both clients, this time it worked on both ends

However, the actual encrypted message, despite all the now corrected errors, still doesn't get through

On testuser2, looking at the 3 dots menu and info

I try to send a message again, for no apparent reason, now it works ?!

The message is received on testuser3

testuser2 OMEMO account info page

testuser3 OMEMO account info page

Just spotted an error message on the testuser3 account page

This error remains, however, encrypted OMEMO messaging seems to work in both direction

It works both ways but error "ConnectionResetByPeer" remains only on testuser3

On testuser3 , I have tried swapping between those two identical chats, see if extraneous messages will appear in the "real" chat

One extraneous message appeared

I will now try to delete the second chat, which shouldn't exist

I restarted everything and sent a message in both directions

On testuser2, the "bogus" chat is back, despite having deleted it
On testuser3, the message orders has somehow gotten scrambled !? some messages from 00H03 received after messages from 01H26 !!

Very strange, I have no idea, I can only provide screenshots

I have difficulty making heads and tails of this problem !

NOTE : version 0.40.1.0 is this the latest ? I can't tell because of the windows store shenenigans
BTW I am running windows 10 (will probably never upgrade to windows 11, too much spyware in there)

Ok one last check, I will try sending files in both directions

... never mind, I can't figure out how to send files, drag and drop shows "forbidden" symbol and I see no attachement icon. Is there a file sending function in UWPX ? Now I remember, this is why we abandonned UWPX for gajim/conversation. We were having the OMEMO problems and then we realized filesharing didn't seem to work. And we really needed filesharing more than anything else so we gave up.

But I do like the single page layout of UWPX more than the two page layout of gajim. So we will try again some time later, unless we abandon XMPP entirely for something else like maybe matrix/mastodon/signal/jitsi/mattermost ? There are sooo many options I am getting seriously lost here !

Anyway, I hope you can untangle this mess of screenshots I have just created !

thank you for looking into this and making this software, I hope it works out in the end !

[COM8]

Thanks for taking the time to investigate this!
Those are the reasons why OMEMO is not enabled by default right now. With the next update (<7 days) there will be a bunch of OMEMO related fixed that I've been working on while testing interoperability with @melvo in Kaidan.

Yes, deleting chats is broken again... I failed to respect the DB constraints there so I have have to look into this hopefully soon again!

There is currently no file sharing, but I'm working on it: https://twitter.com/i/status/1484980174311591939
No ETA on that one.

Yes, there are a lot of (better) alternatives than XMPP and especially UWPX out there right now and I suggest you take a look at them since I do not think I, as a single dev will be able to implement all those features any time soon. UWPX is just a project I'm doing in my free time without any compensation and to have fun since my daily work is Linux and GTK4.

Nevertheless I really appreciate you feedback!