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

[Fubar1977]

12.1 seems to have fixed Tap to Click on my 14" Pro ? Monterey is still a complete Dumpster Fire otherwise but at least this seems to be sorted for me now. Apple needs to spend less time on pointless feature updates and much more time fixing bugs IMO. Not as if they lack the resources!

 

[apple_tap_to_click_sucks]

12.1 seems to have fixed Tap to Click on my 14" Pro ? Monterey is still a complete Dumpster Fire otherwise but at least this seems to be sorted for me now. Apple needs to spend less time on pointless feature updates and much more time fixing bugs IMO. Not as if they lack the resources!

12.1 did fix tap to click on 14” MBP but it didn’t fix “cmd + tap” (takes multiple attempts to open link in background) and pinch to zoom (still unreliable). Can you check if these two are working for you? I’d bet they’re not. And if so, please file a report via the feedback assistant. Thanks.

 

[Fubar1977]

12.1 did fix tap to click on 14” MBP but it didn’t fix “cmd + tap” (takes multiple attempts to open link in background) and pinch to zoom (still unreliable). Can you check if these two are working for you? I’d bet they’re not. And if so, please file a report via the feedback assistant. Thanks.

They seem to be working reliably now too. I think that's what's so annoying about this issue is that it's so inconsistent. It seems to effect otherwise seemingly identical machines to different degrees.

 

[apple_tap_to_click_sucks]

Just updated to 12.2 beta. Confirming that it does not fix the broken `cmd + tap` behavior. The feedback assistant does still say "potential fix identified for a future OS update" so let's see...

 

[Traffy]

Just updated to 12.2 beta. Confirming that it does not fix the broken `cmd + tap` behavior. The feedback assistant does still say "potential fix identified for a future OS update" so let's see...

Are we sure it’s not hardware ? I’m starting to lose patience here …

 

[apple_tap_to_click_sucks]

Are we sure it’s not hardware ? I’m starting to lose patience here …

It's possible there are some underlying hardware issues involved. That doesn't necessarily mean it can't be fixed by tuning it carefully via software - the `tap to click` which was before unreliable has gotten fixed for me after 12.1. That said, consider the following:

- `cmd + tap` is fixed on almost all 13" M1 devices.
- `cmd + tap` is not an issue on 16" M1 Pro devices.
- `cmd + tap` is also fixed on *some* 14" M1 Pro devices, but not all (I'm in the not fixed bucket)

My most plausible theory is that Apple screwed the trackpad sensitivity in manufacturing some of these 14" devices and is now having to tune it out via software, which understandably, is going to be tricky.

Either way, if `cmd + tap` isn't fixed soon, I will consider going back to M1 Air (was a perfect device tbh) until Apple gets its sh*t together on their $2,000+ MBPs.

 

[racostaf]

But keep in mind, is not only the three times... if u wait 3 secs and press one, works...

Definitely, not hardware issue.

 

[pdanford]

I discovered a solution to CMD + tap (and SHIFT + tap):

On the built-in trackpad, there's a central rectangle area a bit smaller than the size of the smaller trackpads older macbooks had before they started putting these massive ones in. The 3-taps required to get CMD + tap to register can be avoided by clicking in this central region instead of more toward the edges. Also note that the first tap must be in this central region. If you first click more toward the outside and it misses it, the trackpad will also reject a followup central tap.

Before that, CMD + tap routinely took 3 taps to multi-select files in Finder. And of course, if I forget and do CMD + tap more toward the edges, 3 it is again. So this required a bit of retraining for me to use the smaller central rectangle region for tap to click, but it's comfortable now.

Now I only use the larger area outside that smaller central rectangle area for continuing long drags. Some might say this is more of a workaround than a solution, but it saved my sanity.

It's almost as if the driver that rejects trackpad input while a key is pressed is working off the dimensions of the older model macbooks' trackpad dimensions.

All this is on:
- 2019 16" MacBook Pro
- built-in trackpad
- Catalina, Big Sur, and Monterey 12.1

Peter

 

[apple_tap_to_click_sucks]

But keep in mind, is not only the three times... if u wait 3 secs and press one, works...

Definitely, not hardware issue.

yeah, that's right. let's hope it gets fixed in software soon.

I discovered a solution to CMD + tap (and SHIFT + tap):

On the built-in trackpad, there's a central rectangle area a bit smaller than the size of the smaller trackpads older macbooks had before they started putting these massive ones in. The 3-clicks required to get CMD + tap to register can be avoided by clicking in this central region instead of more toward the edges. Also note that the first tap must be in this central region. If you first click more toward the outside and it misses it, the trackpad will also reject a followup central tap.

Before that, CMD + tap routinely took 3 taps to multi-select files in Finder. And of course, if I forget and do CMD + tap more toward the edges, 3 it is again. So this required a bit of retraining for me to use the smaller central rectangle region for tap to click, but it's comfortable now.

Now I only use the larger area outside that smaller central rectangle area for continuing long drags. Some might say this is more of a workaround than a solution, but it saved my sanity.

It's almost as if the driver that rejects trackpad input while a key is pressed is working off the dimensions of the older model macbooks' trackpad dimensions.

All this is on:
- 2019 16" MacBook Pro
- built in trackpad
- Catalina, Big Sur, and Monterey 12.1

Peter

just tried this, unfortunately, doesn't seem to help at all on the 14" MBP. As a workaround, I've sort of defaulted to `cmd + click` - at least it works every time, even if it isn't ideal for me. I'm firmly in the camp that taps are superior to clicks, because for an action that we take hundreds/thousands times a day, the least friction/energy UX is the better one, and that's what `tap to click` is.

 

[Traffy]

Yeah I use cmd + click now instead of cmd + tap.

 

[Bustycat]

I don’t think it has been 100% fixed.

 

[pdanford]

just tried this, unfortunately, doesn't seem to help at all on the 14" MBP. As a workaround, I've sort of defaulted to `cmd + click` - at least it works every time, even if it isn't ideal for me. I'm firmly in the camp that taps are superior to clicks, because for an action that we take hundreds/thousands times a day, the least friction/energy UX is the better one, and that's what `tap to click` is.

hmmm. My CMD + tap workaround has worked on every MacBook Pro's built-in trackpad I've tried it on. To confirm, are you on Monterey 12.1, and when you tap with CMD the key down, it's in the very center of the trackpad area (with no failed tap-to-click attempts nearer the edges immediately beforehand)?

 

[apple_tap_to_click_sucks]

hmmm. My CMD + tap workaround has worked on every MacBook Pro's built-in trackpad I've tried it on. To confirm, are you on Monterey 12.1, and when you tap with CMD the key down, it's in the very center of the trackpad area (with no failed tap-to-click attempts nearer the edges immediately beforehand)?

have you tried on a 14" MBP though? This device does seem to uniquely have some problems that are reportedly fixed on others. and yes, I can confirm that I'm on 12.1 (now 12.2 but I tried this on 12.1 already) and that I tested this in exactly the way you described. Anyway, as I mentioned, `cmd + click` is the better workaround I think, in the meantime.

 

[racostaf]

I just went to a store where they sell macs and I was able to reproduce the same behavior ... 14" MBP

 

[pdanford]

have you tried on a 14" MBP though? This device does seem to uniquely have some problems that are reportedly fixed on others. and yes, I can confirm that I'm on 12.1 (now 12.2 but I tried this on 12.1 already) and that I tested this in exactly the way you described. Anyway, as I mentioned, `cmd + click` is the better workaround I think, in the meantime.

I think what others reported as fixed was the tap-to-click in general (not the CMD + tap special case). I'd guess the ones that do report CMD + tap as working happen to be taping near the center of the trackpad, so they wouldn't have seen the 3-tap problem - which currently still very often doesn't work as of Monterey 12.1 when you CMD + tap too far from the center.

Before, I had tried CMD + click instead of CMD + tap, with tap for everything else, and it was pretty jarring switching between tap/click modes until I figured out that central region deal workaround.

The 14" MBP is one I haven't tested on yet, but I'm asking around to see if anyone I know has one. If so, I'll report back. In any case, I hope you don't have to endure too long; I can really sympathize

 

[apple_tap_to_click_sucks]

Just updated to 12.2 beta. Confirming that it does not fix the broken `cmd + tap` behavior. The feedback assistant does still say "potential fix identified for a future OS update" so let's see...

Update on this: the status changed to 'potential fix identified - in MacOS 12.1'. I'm already on 12.2 beta and the 'cmd + tap' is obviously nowhere near fixed. Not a good sign, and I think this likely means that they've called it a day after "fixing" tap to click in 12.1 (which only fixed the taps, not the modifier key + taps on 14")

Time to get rid of this device and revert to MacBook Air or something? Don't have much hope that they're working to fix this anymore. All the other reports I filed specifically about `cmd + tap` issue are still saying "no similar reports" :/

 

[Traffy]

Update on this: the status changed to 'potential fix identified - in MacOS 12.1'. I'm already on 12.2 beta and the 'cmd + tap' is obviously nowhere near fixed. Not a good sign, and I think this likely means that they've called it a day after "fixing" tap to click in 12.1 (which only fixed the taps, not the modifier key + taps on 14")

Time to get rid of this device and revert to MacBook Air or something? Don't have much hope that they're working to fix this anymore. All the other reports I filed specifically about `cmd + tap` issue are still saying "no similar reports" :/
View attachment 1931463

I have the same update. Potential fix identified. In macOS 12.1. Maybe we should open a new feedback with Cmd + Tap to click isn't working on Monterey 12.1 in the title ?

 

[apple_tap_to_click_sucks]

I have the same update. Potential fix identified. In macOS 12.1. Maybe we should open a new feedback with Cmd + Tap to click isn't working on Monterey 12.1 in the title ?

Yes, I opened another one already. You should too.

 

[artmilitonian]

Hi everyone!

On my new (actually its a second new mac) MacBook Pro 14" I have a problem with "tap to click". If I press on keyboard Shift or CMD and want to tap on trackpad - first two taps doesn't work. Only on 3rd tap - action is on.

I bought my MB in middle at November and when it arrived at december, because I order custom configuration (with MacOS 12.0.1) - I found trackpads problem. Apple Advisors run remote diagnostic and found "NDR006" issue ("may be an issue with the trackpad"). They said that the Mac has a manufacturing defect and offered to replace it.

After ~3 weeks I got my new MB Pro. And immediately after unpacking, I found same problems with the trackpad. Mac with MacOS 12.0.1, I thought that the problem in this case is definitely with the system.

On MacOS 12.1 the problem is still on. And diagnostic not found any problems.

You'll laugh, but I went to the nearest store and found the same trackpad problems on the Macbook 14 (MacOS 12.1) in the showcase.

 

[Traffy]

Hi everyone!

On my new (actually its a second new mac) MacBook Pro 14" I have a problem with "tap to click". If I press on keyboard Shift or CMD and want to tap on trackpad - first two taps doesn't work. Only on 3rd tap - action is on.

I bought my MB in middle at November and when it arrived at december, because I order custom configuration (with MacOS 12.0.1) - I found trackpads problem. Apple Advisors run remote diagnostic and found "NDR006" issue ("may be an issue with the trackpad"). They said that the Mac has a manufacturing defect and offered to replace it.

After ~3 weeks I got my new MB Pro. And immediately after unpacking, I found same problems with the trackpad. Mac with MacOS 12.0.1, I thought that the problem in this case is definitely with the system.

On MacOS 12.1 the problem is still on. And diagnostic not found any problems.

You'll laugh, but I went to the nearest store and found the same trackpad problems on the Macbook 14 (MacOS 12.1) in the showcase.

Lol welcome. Open feedback assistant in spotlight and write a feedback with “cmd + tap to click not working on Monterey 12.1” in the title.

Edit : This NDR006 issue is worrying me.

 

[dafi]

Updated today anf now I have a new problem under 12.1, very often the double tap doesn't work, fixed the tap but broken the double tap, am I alone?

PS
Believe me but I'm considering to sell all my macs and switch to Linux, stopping to develop using the ugly XCode and fighting with App Store review rules
Please apoligize me for this rant but finding this new bug on a simple device like a trackpad is very frustrating

EDIT: Just to be clear, pairing the magic trackpad to a mac with Big Sur everything works fine so it's a software problem!

 

[artmilitonian]

Also, I have talk with Apple Executive Relations Office and they said "possible software problem".

I asked them "what if the update doesn't help, will you replace the device?"
They replied that they could only do a replacement within the return period. That is, if the update comes out in a month and the problem isn't resolved, I won't be able to replace/return the device. Great!

 

[Traffy]

Also, I have talk with Apple Executive Relations Office and they said "possible software problem".

I asked them "what if the update doesn't help, will you replace the device?"
They replied that they could only do a replacement within the return period. That is, if the update comes out in a month and the problem isn't resolved, I won't be able to replace/return the device. Great!

You are not alone. Go see my post page 13 about the secondary click.

 

[dafi]

Also, I have talk with Apple Executive Relations Office and they said "possible software problem".

I asked them "what if the update doesn't help, will you replace the device?"
They replied that they could only do a replacement within the return period. That is, if the update comes out in a month and the problem isn't resolved, I won't be able to replace/return the device. Great!

But the replaced device will have the same problem, this is an infinite loop

 

[apple_tap_to_click_sucks]

My new report, filed on Dec 20th, went from `recent similar reports: None` to `Less than 10`. Please keep reporting this issue folks, it might be working!

To respond to a few previous comments:

• My first MBP 14" had the same Diagnostics report issue related to the trackpad. Since I was one of the first customers to take delivery of these new devices, there weren't any reports of the bug just yet. So, thinking that it was a hardware problem, I immediately returned and replaced my device with an identical 14" MBP. Guess what, it had exactly the same issues, but it didn't show up that trackpad reference code in the diagnostics.
• Since then, hundreds of people started reporting trackpad bugs, which were actually affecting many of the older M1 and Intel devices too. In 12.1 seed 4, Apple did address the `tap to click` being unreliable, and it got better. Since then, at least it does not miss the taps themselves on my 14".
• However, on many 14", including brand new ones sitting at Apple stores right now, you can go and press `cmd + tap` to, say multi-select, or open a YouTube video in the background, only to watch that tap fail 2 times and only registering on the 3rd attempt. Multiple people have tried going to the store and have confirmed this.

I filed the new feedback report with this title because Apple replied to most people's previous feedback when they released seed 4, and asked us to file new feedback with this given title if it wasn't fixed.

As Traffy suggested above, if you're facing the same issue, make sure to file a report with the title "`cmd + tap to click` is not working in seed 4." And feel free to copy my bug report if you find that easier.