Initiating swipe from read->unread or unread->read causes mark (un)read button to get stuck in the wrong state

[dtmdl]

Checklist

• [X] I have used the search function to see if someone else has already submitted the same bug report.
• [X] I will describe the problem with as much detail as possible.

App version

6.301

Where did you get the app from?

Google Play

Android version

13 build TP1A.220624.014

Device model

Pixel 5

Steps to reproduce

1. Start with a message list containing at least one unread and one read email.
2. Ensure 'mark as read when opened' is disabled.
3. Open the unread email, note the 'Mark as read' button is showing.
4. Initiate a swipe to the read email (just a few pixels), then release.
5. Note that the 'Mark as read' button was replaced with 'Mark as unread' as soon as the swipe was initiated, and remains in that state after abandoning the swipe. Pressing the button appears to have no effect.

Expected behavior

Mark as (un)read button status should remain synchronised with the displayed email.

Actual behavior

Mark as (un)read button status becomes desynchronised.

Note that, after performing multiple (completed) swipes, the bug sometimes seems to go away -- in this scenario the button state does not change until the swipe is completed.

Returning to the message list and opening a mail again appears to reliably trigger the bug every time, for me at least.

Logs

No response