Apple reportedly investigating a 'ghost touches' issue on the newest Apple Watch models

Two Apple Watch 9 models
The Apple Watch 9 is one of the models affected (Image credit: Apple)

Apple is apparently looking into a 'ghost touches' bug on the Apple Watch 9 and the Apple Watch Ultra 2, which (as the name suggests) means that taps and swipes are being registered even when the display isn't being touched.

As per a memo sent to Apple Authorized Service Providers and seen by MacRumors, Apple is aware of the issue and is actively investigating it. If that's the case and Apple is actually taking notice, the problem must be fairly widespread.

That said, we can't find too many reports online from people who've been experiencing this specific problem. The mentions of it that we have discovered aren't particularly recent, though of course not everyone who finds a bug on their Apple device then goes and posts about it on the internet.

"Some customers may report their Apple Watch Series 9 or Apple Watch Ultra 2 is experiencing false touches on their display," says the memo, so it doesn't appear that this is currently affecting older versions of the wearable.

Unwanted actions

Apple Watch Ultra 2 watch face and straps

The Apple Watch Ultra 2 is also involved (Image credit: Apple)

These ghost touches can start phone calls and prevent a smartwatch's passcode from being entered, according to the memo, so if you've been experiencing these problems on your own Apple Watch then you're not alone.

Right now it's not clear what's causing the issue, or when Apple might be able to roll out a fix (if indeed it can be fixed by a software update). It's also not clear just how many users have reported the bug.

If your Apple Watch 9 or Apple Watch Ultra 2 is exhibiting this kind of behavior, at the moment there's no temporary fix that's guaranteed to work for everyone – though Apple's memo suggests that force restarting an affected watch and keeping its software right up to date may help to an extent.

The comments underneath the MacRumors article indicate that a reboot or a hard reset could also help fix the problem, at least for a while. If we hear anything that's more official from Apple, then we will of course let you know.

You might also like

David Nield
Freelance Contributor

Dave is a freelance tech journalist who has been writing about gadgets, apps and the web for more than two decades. Based out of Stockport, England, on TechRadar you'll find him covering news, features and reviews, particularly for phones, tablets and wearables. Working to ensure our breaking news coverage is the best in the business over weekends, David also has bylines at Gizmodo, T3, PopSci and a few other places besides, as well as being many years editing the likes of PC Explorer and The Hardware Handbook.

TOPICS