Open bitmold opened 7 months ago
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.
I'll see you in hell, stale bot
Envoyé depuis Proton Mail mobile
-------- Message d'origine -------- Le 29 févr. 2024, 10:36 PM, stale[bot] a écrit :
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.
— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: @.***>
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.
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.
Still occurs On Thursday, July 4th, 2024 at 3:24 AM, stale[bot] @.***> wrote:
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.
— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: @.***>
I think this is the same underlying issue causing swiping or long-pressing to reply on a message from an unregistered user causes the message to become stuck as a draft. Would love to see this fixed.
Bug description
If you leave a group chat with an unsent message, on the home screen that message will still appear as a draft. If you reopen the exited group it will propagate to the top of your messages since the app still treats it as having a drafted message
Steps to reproduce
Expected result: Once you leave the group your draft, which is forever inaccessible as the bug now stands, should be cleared too.