watchOS 26 — Dismissing a message does not mark it "read"

[PotentPeas]

I don't know how many people actually do this, but I use it all of the time.

When a message notification comes in (iMessage or SMS), if I swipe DOWN when the notification is open on my watch, a little "Dismiss" arrow pops up at the top. If I dismiss the message in this manner (rather than just pressing the digital crown or letting it expire), the message is marked "read". There won't be any little unread bubbles for that message on my phone or Mac.

Well, that is how it used to work. With watchOS 26, I can still dismiss the message in this manner, but it does not get marked read. It is still showing as unread on my other devices... and on my watch as well. I have to actually "open" the message thread to get it to be marked read.

Anyone else? Wanting to see if this is "just me" before I go whine to Apple.

 

[BriceApp]

I have noticed the same thing through out the beta and now with the release. It is annoying, because I am used to dismissing them and they being marked as read.

 

[crdav]

I reported this during the beta, and it said “potential fix identified” for a future release - wasn’t fixed in the RC nor the final build. But Apple are aware so hopefully soon!

 

[PotentPeas]

Thanks for the confirmation.

I reported as well. I don't know if it will do any good but I will continue to report after every update if this is not fixed.

(I have reported some other specific reproducible bugs in watchOS in the past that did end up getting fixed. Here's hoping!)

Sigh. I knew I should have waited for 26.1 or 26.2. But I really wanted to play with that call screening feature...

 

[Haxley]

What’s worse is even if you tap the notification and read the text in the messages app, it still doesn’t mark it as read. You have to go out, then go back in and read it again.

 

[PotentPeas]

Testing iOS + watchOS 26.1 beta 2. This issue is still present.

[Edit]
Likewise with 26.1 beta 3.

 

[DesertSilver]

Issue still present with my phone and watch both being on the 26.1 RC versions that came out yesterday. Annoying.

 

[xpxp2002]

Really disappointed to hear that this hasn't been fixed.