self-destruct message is too fast

[juanpc2018]

trafficstars

Guidelines

• [X] I have searched searched open and closed issues for duplicates
• [X] I am submitting a bug report for existing functionality that does not work as intended
• [X] This isn't a feature request or a discussion topic

Bug description

Dissapearing messages when set to 30 seconds or more, on the sender side "Apple iOS", i have the receiving device "Android 8", turned off, no expire time limit.

When i turn-on, log in, connect to wifi, later... next day A preview of the message notification appears on the Android Drop down menu, When i click/touch the message preview notification to see the complete message in Signal apk, Message is Gone, No 30 seconds, no 5min, no 1 day. 0 seconds.

Problem #2.

This Android phone Time gets out of sync if battery is critical, and phone is off for a while.. The more time is off, the more gets out of sync.

To sync time again to internet time, requires several hours for android os to re sync time automatically, or requires manual override.

But Signal message is received No matter what. Sometimes reply arrives before question. Like grandfather paradox.

Signal does Not give a Warning that time is out of sync.

2 problems in 1.

Screenshots

No response

Device

No response

Android version

No response

Signal version

No response

Link to debug log

No response

[Ascheidweiler]

I was trying to replicate the first one on an Android 15.0 Pixel 7 emulator, but the message appeared as expected. When you say Android 8, do you mean the Android 8.0 Oreo API that is out of support by Google, or do you mean a Pixel 8 emulator with a more up to date OS?

For the second, it's generally standard practice to open a second Issue for a separate problem. I would imagine that's the case for this project, too.

[EphDoering]

I believe the timer starts when the server receives the message, or possibly from the timestamp of message creation. So it's expected that the message would already be expired as soon as it arrived. You should be able to see the timer ticking down on the sending device that confirms this. The way you said the receiving device had no time limit makes me think you're not understanding how the setting works. The setting is per conversation, in both directions. So both people in the conversation will see the same timer setting changes and the messages will expire for both/all participants at the same time. If that time is before you get a chance to see it... well that's working as intended.

[greyson-signal]

The timer starts when the receiver views the message (yes, that means that the message will expire for different people at different times). So the behavior OP reported is not correct. However, it seems like the two issues they reported around clock drift would be very-much related. If OP had marked the message read or viewed the message somehow, then their system clock jumped around, it could cause the message to instantly expire.

It's hard to say without a log. We could do better with alerting to people when their system time is far off from "real time".

[stale[bot]]

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.

[stale[bot]]

This issue has been closed due to inactivity.