You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While having a channel open, the most recent received message will sometimes show as "This message is not decrypted yet", see screenshot.
After receiving another message, the previous message will show correctly, but the newest message might maybe show as "This message is not decrypted yet".
Reproduction
The most reliable way I've found to reproduce is:
Have two Cinny clients open side by side, logged in with the same user
Send a message on one client
The other client (most of the time) will show the "This message is not decrypted yet" message
A less complicated way to reproduce is to have someone message you, but that doesn't seem to be causing the issue every time.
Expected behavior
To show the message instead of "This message is not decrypted yet"
I can confirm that the "This message is not decrypted yet" message is being replaced with the decrypted message very quickly when using the PR-version of cinny. The PR fixes the issue for me.
Describe the bug
While having a channel open, the most recent received message will sometimes show as "This message is not decrypted yet", see screenshot.
After receiving another message, the previous message will show correctly, but the newest message might maybe show as "This message is not decrypted yet".
Reproduction
The most reliable way I've found to reproduce is:
A less complicated way to reproduce is to have someone message you, but that doesn't seem to be causing the issue every time.
Expected behavior
To show the message instead of "This message is not decrypted yet"
Platform and versions
Additional context
A workaround is to switch to a different channel and back again, then the message shows correctly.
I've also tested a PR of a friend after talking to them about this issue a little bit, and it seems to fix this issue: #1992
The text was updated successfully, but these errors were encountered: