[X] I have searched searched open and closed issues for duplicates.
[X] I am using Signal-Desktop as provided by the Signal team, not a 3rd-party package.
Overall summary
If a (linked and up to date) instance of desktop is not running while a story is posted and replied to, and is also not started again until after the story expires, the reply will be missing from the chat history. This seems to be a bug because the behaviour is different if the desktop instance is started before expiry; in that case the reply will load, and will remain in the history after story expiry with the expected "No longer available" for the quoted story.
Steps to reproduce
Start desktop and ensure it is linked and up to date
Close desktop
On mobile, post a story and have a third party reply to it, or reply to someone else's story that has been posted at some time after step 2.
Wait until the story expires
Start desktop
Expected result
Story reply should be in history with "No longer available" for the story
Actual result
Story reply is not loaded in history at all, even though non-story-reply messages for that 24hr period still are.
Using a supported version?
Overall summary
If a (linked and up to date) instance of desktop is not running while a story is posted and replied to, and is also not started again until after the story expires, the reply will be missing from the chat history. This seems to be a bug because the behaviour is different if the desktop instance is started before expiry; in that case the reply will load, and will remain in the history after story expiry with the expected "No longer available" for the quoted story.
Steps to reproduce
Expected result
Story reply should be in history with "No longer available" for the story
Actual result
Story reply is not loaded in history at all, even though non-story-reply messages for that 24hr period still are.
Screenshots
No response
Signal version
7.4.0
Operating system
Windows 11
Version of Signal on your phone
7.1.3
Link to debug log
No response