-
Notifications
You must be signed in to change notification settings - Fork 24
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[OMEMO] Keep getting the message "Encryption is disabled" even though it is enabled and works. #92
Comments
usually it happens on receiving of unencrypted messages iirc |
I have already informed about this problem. |
Ah good, what's the issue id? |
@SharkyRawr: I am happy that you confirm one OMEMO bug, I am not alone to create tickets :) I have informed @tehnick by several tickets and in the MUC Room ^^ Some tickets: |
@kssytsrk: Can you look this ticket? |
shouldn't this be closed as duplicate of psi-im/psi#616? Or that one closed instead, since psi-im/plugins is a better location compared to psi-im/psi. |
Some tickets from psi repo must be transfered into plugins repo ^^ |
@SharkyRawr: Can you confirm that the OMEMO button icon for the chat tab is enabled? |
Yes it is lit up, clicking it shows the option to disable encryption among other things. The enabled/disabled messages are still happening. |
Yeah, this is happening for me too. I'm on macOS Monterey 12.6.2, and it's doing the same thing as the above screenshot. |
@SharkyRawr, @lunaisnotaboy: Have you tested with latest Psi+ build? |
@Neustradamus I appreciate your efforts but you ping a lot of people in vain |
Because of this issue, I gave up on XMPP altogether. I can try again with a new account, but it'll be a few days because of how busy I am. |
The plugin keeps showing notices in the chat, alternating between
OMEMO encryption is enabled
when I receive a message andEncryption is disabled
when I send a message. Keys are set-up and trusted and I have no idea why this happens. The other party confirmed the message was encrypted.The text was updated successfully, but these errors were encountered: