When a message comes in and a toast pops up with the ability to mark read or quickly reply, if I've entered some text and another message comes in, the next message's toast obliterates the one I was typing. No draft is saved.
Actual result: The 2nd message's toast pops up over the first one, and the message being entered into the first toast disappears.
Expected result: Preferably the 2nd message would be queued (or perhaps extend the toast vertically, if that's an option?), or at least a draft would be saved. Either of these options are not the greatest UX though.
Device: I don't like sharing this info publically
Android version: 7.1.2 (LineageOS 14.1)
Signal version: 4.6.1
I don't currently have one - time crunch this morning - and not sure it will be useful, but if so, I will set up with a friend to induce this bug later today or tomorrow.
probably duplicate of https://github.com/WhisperSystems/Signal-Android/issues/4729
@p4nci I don't think so, the issue you link mentions the text eventually comes back. In this issue however, it never does.
Edit: I can confirm that receiving a message from another sender than the one you are replying to also causes the message to vanish
@Dyras can only partially confirm
Just to make it clear for everybody: you aren't talking about Signal's own implementation of a quick reply window (first screenshot) but about the quick reply function introduced with Nougat (second screenshot).
quick reply < Android 7

quick reply >= Android 7

I am referring to the Android 7 one, yes.
It sounds like this issue is related to #6050 and would be improved by implementing the requested feature.
Dupe of #6042 ? and both will be fixed if #6050 is addressed?
I think this is a dupe of #6042, although more discussion has accrued in this issue now.
I wanted to clarify when the text is completely lost.
If you receive a message from the same contact, it pops over the toast but the text can be salvaged by hitting 'reply' and loading the full app's reply UI.
It occurs to me that this bug could perhaps be avoided quite simply by never having a toast pop over one that already exists, or that the user is currently interacting with.
GitHub Issue Cleanup:
See #7598 for more information.