Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
I've run each full release and every developer beta for years on various Macs, and this issue is absolutely more pronounced on the most recent beta (21C5039b) on my M1 MBP. Double or triple tapping to get a response is maddening.
 
I've run each full release and every developer beta for years on various Macs, and this issue is absolutely more pronounced on the most recent beta (21C5039b) on my M1 MBP. Double or triple tapping to get a response is maddening.
I feel you. This is not acceptable. It almost makes me want to return the macbook. I just tapped twice to send this reply.
 
Same here. Macbook pro 16 2019 on the latest 12.1 public beta. I had to turn off tap to click, the mac was unusable and I noticed it was getting worse and worse over time.
 
For those that don't know there's an alternative action.... go to Settings> Trackpad> deselect Tap to Click.

So instead of a light tap, you'll just press down instead like you would with a mouse button.

50% of my taps were ignored, it was intolerable, so I just turned that off. If this issue drives you nuts... just turn it off. You get used to the new way soon enough.
 
  • Like
Reactions: Pug72 and Smoothie
For those that don't know there's an alternative action.... go to Settings> Trackpad> deselect Tap to Click.

So instead of a light tap, you'll just press down instead like you would with a mouse button.

50% of my taps were ignored, it was intolerable, so I just turned that off. If this issue drives you nuts... just turn it off. You get used to the new way soon enough.
Sorry but it makes no sense. Disabling the feature is not an option. We shouldn't have to change our workflows or the way we use the machines we paid for because the developers broke one of the most basic functionalities. This is far from being a solution. We (the ones complaining about it) rely on tap to click and should not have to click because they messed up some simple feature.
 
Sorry but it makes no sense. Disabling the feature is not an option. We shouldn't have to change our workflows or the way we use the machines we paid for because the developers broke one of the most basic functionalities. This is far from being a solution. We (the ones complaining about it) rely on tap to click and should not have to click because they messed up some simple feature.
What are you talking about? In response to people who've actually submitted a bug report, Apple has said they're working on a fix for distribution in a future update. He's offering a workaround until Apple fixes this. I've also turned off tap-to-click for the time being and my MBP is usable. Once the fix is distributed, I'll re-enable it.
 
No, Apple just indicated they identified a potential fix within an upcoming OS update. This doesn't mean the fix will be included in the next release. I already had such notes in previous bug reports, and it often took a couple of months until the issue was finally fixed.
 
I just bought a used M1 MBA from a friend, drove home and wiped and reloaded it, and 'Tap to Click' isn't working properly. I rebooted, same thing. Oh come on, what? Is this machine faulty, did I get snookered?

Then I found this thread and all my worries disappeared, I don't know if I have ever been happier to read that there's a bug in the new MacOS release. I don't care how long it takes to get fixed.
 
Not fixed in 12.1 Beta 3. Every unmarked app is a tap to click failure. It somehow feels even worse now in B3.
View attachment 1911839

Edit: Yep, definitely got worse in Beta 3. Tap to click is totally unusable now on my M1 MBP.
Edit 2: I never had issues with swipe gestures until now. With Beta 3 those don't work reliably anymore as well. Swiping left or right to switch desktops repeatedly fails or causes jumps in the wrong direction.
Edit 3: Pinch to zoom also stopped working reliably. It doesn't do smooth movements anymore and often forgets about the second finger and moves the pointer instead. This really feels like one of those crappy touchpads in cheap low-budget laptops from China.

Same is my experience with Monterey on 2021 MBP 16 inch. Out-of-box 12.0 worked fine without issues. Update to 12.0.1 started causing issues and the 12.1 beta 3 has taken it to the next levels. Tim needs to do a Good Morniiiiing with his developers and get this sorted.
 
Same is my experience with Monterey on 2021 MBP 16 inch. Out-of-box 12.0 worked fine without issues. Update to 12.0.1 started causing issues and the 12.1 beta 3 has taken it to the next levels. Tim needs to do a Good Morniiiiing with his developers and get this sorted.
I haven't updated my 16-inch M1 Pro. It's still on 12.0 and it exhibits the tap-to-click bug. The reason I haven't updated is that 12.0.1 introduced a fast charging issue for the 16-inch M1. This is the subject of a thread in the Apple Silicon forum.
 
This hasn't been fixed for how many weeks...maybe Apple isn't paying the developers enough. That must be it.
 
I haven't updated my 16-inch M1 Pro. It's still on 12.0 and it exhibits the tap-to-click bug. The reason I haven't updated is that 12.0.1 introduced a fast charging issue for the 16-inch M1. This is the subject of a thread in the Apple Silicon forum.

That bug is not a showstopper. It is only about when the computer is shut off and you try to charge it. At least that's what I find the issue to be. Rest there is no issue with fast charging as I could find.
 
That bug is not a showstopper. It is only about when the computer is shut off and you try to charge it. At least that's what I find the issue to be. Rest there is no issue with fast charging as I could find.
I suppose one could argue that any bug that can be avoided by working around it isn't a showstopper. However, that bug IS triggered by fast charging since it only occurs when the battery is below 80 percent and the 140 watt adapter is attached to the MagSafe port, thus initiating fast charging. Yes, you can avoid it by not shutting down the MBP before attaching the power adapter, but it's still a bug that Apple introduced in 12.0.1 and it took a number of people contributing to that thread to determine what was triggering the bug.

This is why I usually wait for a few point releases before updating to a new OS. My 2017 iMac is still running Big Sur and is very stable. But my new MBP came with Monterey, so I had no choice in the matter.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.