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
Note: this should probably go under lokinet or oxen-core, but a quick glance at their current issues made me hesitant to post there. Devs, please move it where it belongs.
Describe the bug
A clear and concise description of what the bug is.
Alice communicates with Bob via Session. The "Disappearing messages timer" is set.
Alice has two devices, X and Y. Alice uses mostly X and only seldom Y.
Bob has only one device, Z.
Alice chats with Bob using X, respectively Z. The countdown for the disappearing messages starts as soon as they're read and, after a while, the messages disappear from X and Z (as intended).
Some time later (but within the 14-day period after the first message was exchanged), Alice powers on Y - and the expired messages are downloaded onto Y; the countdown starts anew on Y.
Expected behavior: expiration status should be kept on the Oxen network. Y should not download the messages that have been already read and disappeared,
Steps to reproduce the behavior.
Link multiple devices to the same conversation;
Set a disappearing messages timer;
Wait for messages to disappear on one device;
Turn on another device linked to the conversation.
The text was updated successfully, but these errors were encountered:
Hi @smss2022 , thanks for the feedback. We are working on rebuilding the disappearing messages. The rebuild will help with this issue. Will keep you posted once we finish the rebuild. Cheers!
Closing this as #731 is now live and this issue was related to the legacy version. Feel free to open a new issue if you experience any problems like this with the updated version of Disappearing Messages
Note: this should probably go under lokinet or oxen-core, but a quick glance at their current issues made me hesitant to post there. Devs, please move it where it belongs.
Describe the bug
A clear and concise description of what the bug is.
Alice communicates with Bob via Session. The "Disappearing messages timer" is set.
Alice has two devices, X and Y. Alice uses mostly X and only seldom Y.
Bob has only one device, Z.
Alice chats with Bob using X, respectively Z. The countdown for the disappearing messages starts as soon as they're read and, after a while, the messages disappear from X and Z (as intended).
Some time later (but within the 14-day period after the first message was exchanged), Alice powers on Y - and the expired messages are downloaded onto Y; the countdown starts anew on Y.
Expected behavior: expiration status should be kept on the Oxen network. Y should not download the messages that have been already read and disappeared,
Steps to reproduce the behavior.
The text was updated successfully, but these errors were encountered: