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
if you set a global disappearing message timer before you have any notes to self, than tap the write new message button and open notes to self, you find a warning at the top "as soon as you send a message the disappearing timer will be set to x" or something alike.
two issues:
If you go into chat settings the timer is already set to "off" you can't turn it off. But in reality it is on. You have to first send a message and only after that come back to chat settings and turn it off again.
You can select the status message about the notification timer, but you do not have a delete option for it, or any option at all really. It should be deletable.
Screenshots
Device info
Device: Manufacturer Model XVI Android version: 10 Signal version: 7.9.6
Link to debug log
The text was updated successfully, but these errors were encountered:
Meteor0id
changed the title
/niot possbile to turn off disappearing messages in note to self before sending a first message, and notification cant be deleted either
not possbile to turn off disappearing messages in note to self before sending a first message, and notification cant be deleted either
Jun 23, 2024
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Bug description
if you set a global disappearing message timer before you have any notes to self, than tap the write new message button and open notes to self, you find a warning at the top "as soon as you send a message the disappearing timer will be set to x" or something alike.
two issues:
Screenshots
Device info
Device: Manufacturer Model XVI
Android version: 10
Signal version: 7.9.6
Link to debug log
The text was updated successfully, but these errors were encountered: