Apple Watch SMS Message notification dismiss button

[chrismac2]

I am running watchOS 8 public beta, and on all the betas including the most recent, 90% of the time, when a SMS or iMessage comes in and I get the notification on my watch, I read the notification, and scroll down a little until the "Dismiss" button appears (over the list of canned responses), and no matter how carefully I try to tap the "dismiss" button, it ends up sending one of the canned replies that are directly behind/underneath the button. So I end up sending random, nonsensical replies to people. This was not a problem on watchOS 7. Anyone else?

 

[dbreiser]

Happens to me too on the release version. I kept getting "this account doesn't accept responses" messages from an automated sender until I just hit the crown rather than the 'Dismiss' button. I can see the inadvertent canned responses when I open the conversation on my Mac.

 

[chrismac2]

Yeah the area where you need to touch to actually hit the dismiss button is very narrow, and more towards the top of the button. Now I just turn the crown quickly to scroll past all the canned replies and then tap dismiss. It’s still perilously close to tapping a canned reply but so far it has worked for me. Can’t believe none of the other beta testers complained or experienced the issue.

 

[MrNaKW]

This is happening to me and has never happened in any previous version. So annoying!

 

[bransoj]

I've actually done this a couple of times as well.

 

[ttforever]

Yep me too, got a thread on here but no responses

 

[nok123]

Same here … annoying.

 

[allemattio]

Same here..I'll have to stop using the dismiss button, sent the wrong message too many times, it's not reliable, hoping for a fix

 

[chrismac2]

It appears, with just one Messages notification so far, that the dismiss button is working properly in watchOS 8.1. Can anyone else confirm? I'll be so happy if this is fixed...

 

[Terbor]

It appears, with just one Messages notification so far, that the dismiss button is working properly in watchOS 8.1. Can anyone else confirm? I'll be so happy if this is fixed...

Haven't updated yet. Hope you're right!