Tap-to-click issues on B9 and 10 (and now Monterey release)

[Kafka]

Regarding top 1) are there any known 14“ MBP 2021 where CMD and tap-to-click is working properly since macos 12.1/12.2?

Not sure, but it's not easy to tell because:
- it seems most people do not tap,
- many people probably don't even know the cmd/maj trick.

I just know I'm on my third 14" and they all did this, and the one I played around with in the store did it too.
I'm also considering giving up and returning it, but I'm very annoyed because I need 2 external displays.

 

[bdonkey]

I'm experiencing the exact same issue on my 14" MBP running macOS 12.1. Here's the report I sent in using the "Feedback Assistant" app in macOS:

Title: `cmd + tap to click` is not working

On my new 14” MacBook Pro running macOS 12.1: Using a modifier key, such as CMD, in conjunction with tap-to-click does not work unless the modifier key has been held down for about a second or so; otherwise, the tap-to-click completely fails to register.

This issue was present out-of-the-box from the first day I used the system.

This issue has hundreds of reports in Apple’s and other discussion forums. It’s causing a lot of frustration because I use the “quickly press-CMD and tap-to-click” interaction many times throughout the day to open links in new tabs. This interaction works fine on my other (Intel-based) MacBooks running Catalina 10.15.7.

On the affected system, holding down CMD for about a second before attempting to tap-to-click seems to let the tap-to-click register; it almost seems there is some delay or timer that must expire once a modifier key is held down before the system will recognize a tap-to-click. I’m speculating here, but there might be some issue with palm rejection heuristics interfering with this interaction?

 

[huythanhv2]

Just submitted the same feedback to Apple

 

[apple_tap_to_click_sucks]

Folks, I'm just now seeing what is perhaps the first person to claim that the 12.1 build fixed the `cmd + tap` issue on their 14" MBP. Here.

The comment above says they're on the public build (not beta or developer). Can someone else confirm this either way if you're on a standard public 12.1 release, or are able to go revert back to a public build to test this out on your 14"?

 

[apple_tap_to_click_sucks]

This is what I am seeing too. OS 12.0.1 on a new 14" M1 Pro. Tapping to click by itself seems mostly ok but holding down Command or Shift or Control makes it so the click usually fails to register. It's not restricted to any single application, either. I thought my trackpad was broken and was debating if I should take the laptop in to replace it until I found this thread. Guess it's a bug in the OS.

just trying to get a sense if this was ever fixed on any of the 14" at all? Are you still having the same cmd + tap bug? Which OS build are you on?

 

[huythanhv2]

I'm on public 12.1 and have never been on beta build. This problem still exists for me.

 

[artmilitonian]

Yes, in my MBP 14" still on.
Can anybody connect with Apple and try discuss about this problem?

 

[Juen]

Can confirm. MBP 14" macOS 12.1
Tap-to-Click and unresponsive Trackpad after "Shift"+Trackpad or "CMD"+Trackpad still persists.
Tho it only happens on some occasions. Was worse on 12.0.1.

 

[apple_tap_to_click_sucks]

Folks, we've been struggling with a broken `cmd + tap` for over 2 months now. The software release that was supposed to fix trackpad issues (12.1) came and went away. Us 14" owners are left bag holding these $2000+ devices with a broken core functionality.

I've already sunk enough time into this issue, and at this point, I've decided I'm going to take it to an Apple Store on Thursday with a genius appointment. I'm fully aware they're not going to be able to fix it there, but I will argue to get a full refund on this device (I'm past my return window of course, and someone posted they were able to get it refunded due to this bug even after the return window). I will most likely revert back to my M1 Air - that machine was flawless and never once had shameful bugs like this.

So that's my plan at this stage – don't want to sink more headspace into this frustrating issue while I could be doing more productive things. Will update you guys on Thursday.

 

[taptaptap10]

Folks, we've been struggling with a broken `cmd + tap` for over 2 months now. The software release that was supposed to fix trackpad issues (12.1) came and went away. Us 14" owners are left bag holding these $2000+ devices with a broken core functionality.

I've already sunk enough time into this issue, and at this point, I've decided I'm going to take it to an Apple Store on Thursday with a genius appointment. I'm fully aware they're not going to be able to fix it there, but I will argue to get a full refund on this device (I'm past my return window of course, and someone posted they were able to get it refunded due to this bug even after the return window). I will most likely revert back to my M1 Air - that machine was flawless and never once had shameful bugs like this.

So that's my plan at this stage – don't want to sink more headspace into this frustrating issue while I could be doing more productive things. Will update you guys on Thursday.

any updates on this bro? i have the same problem on a brandnew mac 14 inch. Thinking of returning but don't really want to do that if its just a software issue since i really like the laptop otherwise. Maybe ill just keep it and if its a hardware issue it will probably be fixed in the first year warrantee.

 

[apple_tap_to_click_sucks]

Update: I went to the Apple store into a Genius Bar reservation. Explained the bug to my service rep, was able to replicate in front of her quite easily. Even told her that “I bet the 14” MBPs in this store on demo all have the same issue. We walked to one randomly, and yes it did! She was very helpful and spoke to the manager on behalf of me to initiate a return even though I didn’t fall into the extended return window.

And with that, I said farewell to this 14” MacBook. It’s been a long wait and 16 page thread on this issue for us folks, and I appreciate if you guys want to stick it out. Personally, I’m out. Have my trusty M1 MacBook Air arriving today already! Absolutely loved that machine and never had any issues whatsoever.

 

[taptaptap10]

Update: I went to the Apple store into a Genius Bar reservation. Explained the bug to my service rep, was able to replicate in front of her quite easily. Even told her that “I bet the 14” MBPs in this store on demo all have the same issue. We walked to one randomly, and yes it did! She was very helpful and spoke to the manager on behalf of me to initiate a return even though I didn’t fall into the extended return window.

And with that, I said farewell to this 14” MacBook. It’s been a long wait and 16 page thread on this issue for us folks, and I appreciate if you guys want to stick it out. Personally, I’m out. Have my trusty M1 MacBook Air arriving today already! Absolutely loved that machine and never had any issues whatsoever.

Really curious if your mac air has the same issues. Pinch to zoom also seems to be an issue with air and pro..

 

[Kafka]

Really curious if your mac air has the same issues. Pinch to zoom also seems to be an issue with air and pro..

Mine has zero issue. Btw I finally returned my 14" and picked up a 16", which also has no issue. It really seems to be a 14" problem.

 

[djalix69]

Mine has zero issue. Btw I finally returned my 14" and picked up a 16", which also has no issue. It really seems to be a 14" problem.

Unfortunately its not. I have a 16" and have the issue

 

[s1mpleNtbk]

CMD + TAP To Click does not take effect, such a serious problem has been three months, Apple is not to fix it.

 

[huythanhv2]

If anyone on this thread does update to this https://forums.macrumors.com/thread...of-macos-monterey-12-2-to-developers.2330869/ - please keep us here posted whether there are good news.

 

[s1mpleNtbk]

If anyone on this thread does update to this https://forums.macrumors.com/thread...of-macos-monterey-12-2-to-developers.2330869/ - please keep us here posted whether there are good news.

agree

 

[SoYoung]

How is pinch to zoom in the new beta?

 

[eelpout]

CMD + TAP To Click does not take effect, such a serious problem has been three months, Apple is not to fix it.

same with shift + tap, still an issue on my MBP 14" w/12.1. Guess it's a simultaneous key and touchpad problem. :/

 

[fredwu]

14", latest beta (21D5039d). Things have not changed since the last beta AFAICS. CMD/SHIFT + tap is still broken, pinch to zoom is still unreliable. ;(

My submitted feedback from last beta hasn't gotten any updates from Apple either.

 

[s1mpleNtbk]

14", latest beta (21D5039d). Things have not changed since the last beta AFAICS. CMD/SHIFT + tap is still broken, pinch to zoom is still unreliable. ;(

My submitted feedback from last beta hasn't gotten any updates from Apple either.

I have begun to doubt this is a hardware problem because it only appears in 14 inch.

 

[djalix69]

I have begun to doubt this is a hardware problem because it only appears in 14 inch.

Unfortunately its not. I have a 16" and have the issue

 

[forgetcolor]

I'm on a new 16" MBP M1 Pro Max and have this same issue. Also tried 12.2 beta in case it fixed it, but the problem's still there.

Sadly, due to unpredictable circumstances I didn't get a chance to really play with this new machine until I was just outside the return window. Now I wish I'd just sent it back, as the cmd-tap issue is only one of my problems with it. Others include: keyboard-shortcut Space switching animations are 2x longer with "ProMotion" on, I'm seeing key repeat and keys registering out of order issues on the keyboard (thought that would be fixed post-butterfly!), stuttering scrolling in Chrome on basic sites. All are widely-reported issues. None are fixed in 12.2 beta.

Wish I could return this thing — I suffered through the last generation and its horrible touch bar and keyboard problems and was so excited to finally be rid of all that. But this new 5k machine is doing something I never thought possible: make me want a return to my last laptop (which was the worst I've ever used).

 

[josduc]

iMac 27" from 2017 with a Magic Trackpad same issue. Also on beta (it even got worse!)

 

[coreyward]

I just spoke with a senior advisor at Apple where I demonstrated the issue via ScreenShare, provided a CaptureData dump, and did some additional testing an isolation (e.g. when an external keyboard modifier key is pressed, the internal trackpad exhibits the issue, but an external trackpad does not exhibit this issue under any circumstances). Here are a few takeaways:

1. The advisor I spoke with was not able to find any existing issues, but might be directed to something once the engineering team takes a look at the fully compiled report.
2. Using the full “click” on the internal trackpad works normally for me. It is only the “tap to click” that has an issue with my configuration. This may or may not be the case for others.
3. This works with ANY key—e.g. in a text field, press and hold a letter key (e.g. “z”) and quickly tap elsewhere in the field to move the insertion cursor. These taps will be ignored for the first few hundred milliseconds as with modifier keys.

For posterity, I am on an MBP 14" M1 Max running macOS 12.1 and have been experiencing this since I received the computer in early December.