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
This isn't a feature request or a discussion topic
Bug description
When sending a scheduled message to a person you have never exchanged messages before, the disappearing messages setting is set, according to your default setting, before the actual message has been sent. I have not yet confirmed if the other person sees the disappearing messages setting change but I'm fairly confident they do, as my desktop signal app saw the change (and bumped this chat to the top of the list). I have confirmed that also the other person gets the notification about the dissappearing messages setting changing in the chat.
I am not 100% sure that this is a functionality that does not work as intended, but to me it seems like a bug as I am not expecting the other person to get any notification before the scheduled send time, I mean I could cancel the message until then.
I am using Signal on an Android running LineageOS 19.1 (Android 12) without google services. I have not tested on other devices to figure out if the bug is maybe related to google services/push notifications.
Steps to reproduce
Set a default disappearing messages time for new chats in the privacy settings.
Schedule a message to be sent later to a signal user you have not exchanged anything before (and maybe you are not in each other contact lists? I don't know if this affects it).
Watch as by the time you press schedule send, the disappearing messages setting is suddenly set and sent to the other person too.
Actual result: Disappearing messages setting is set before the first message is being sent (probably hours before, or at an inconvenient time). Expected result: The dissappearing messages setting should be applied to the chat just at the moment the message is sent. After all, nohing is supposed to leave your device when you schedule a message, right?
Screenshots
Doesn't prove anything but here it goes.
Device info
Device: Xiaomi Poco F3 Android version: 12 (LineageOS 19.1) Signal version: 7.1.3
Link to debug log
I don't think it's needed but I can reproduce it and sent it later if yes (i'm omitting for privacy reasons).
The text was updated successfully, but these errors were encountered:
Bug description
When sending a scheduled message to a person you have never exchanged messages before, the disappearing messages setting is set, according to your default setting, before the actual message has been sent.
I have not yet confirmed if the other person sees the disappearing messages setting change but I'm fairly confident they do, as my desktop signal app saw the change (and bumped this chat to the top of the list).I have confirmed that also the other person gets the notification about the dissappearing messages setting changing in the chat.I am not 100% sure that this is a functionality that does not work as intended, but to me it seems like a bug as I am not expecting the other person to get any notification before the scheduled send time, I mean I could cancel the message until then.
I am using Signal on an Android running LineageOS 19.1 (Android 12) without google services. I have not tested on other devices to figure out if the bug is maybe related to google services/push notifications.
Steps to reproduce
Actual result: Disappearing messages setting is set before the first message is being sent (probably hours before, or at an inconvenient time).
Expected result: The dissappearing messages setting should be applied to the chat just at the moment the message is sent. After all, nohing is supposed to leave your device when you schedule a message, right?
Screenshots
Doesn't prove anything but here it goes.
Device info
Device: Xiaomi Poco F3
Android version: 12 (LineageOS 19.1)
Signal version: 7.1.3
Link to debug log
I don't think it's needed but I can reproduce it and sent it later if yes (i'm omitting for privacy reasons).
The text was updated successfully, but these errors were encountered: