• Source:JND

Cupertino-based tech giant Apple announced its iOS 17.4 update for iPhone recently. Apart from the handset, the company also introduced a new update for its smartwatch. Beyond new features and enhancements, the update has addressed the ghost touch bug on the Apple Watch Series 9 and Ultra 2 that users complained about on social media.

Users of an Apple Watch can download the watchOS 10.4 update via an iPhone running iOS 17. The watchOS 10.4 introduces new emojis, just like what was offered on the Apple iPhone. In the new update, the company also added the option to disable Double Tap when a wearer is using a Vision Pro headset. Plus, an option to expand notifications using Double Tap also debuted in the new package.

Also Read: iPhone 15 Series Covers: Apple Adds Fresh Hues In Latest iPhone Silicone Cases, New Shades For Apple Watch Bands Tag Along

The other improvements include a fix for false touches on the Apple Watch Series 9 and Apple Watch Ultra 2. Apple's release note stated that the update resolved "an issue that causes some users to experience false touches on the display". A bug that prevents contacts from syncing was also addressed in the update.

Users must ensure their Apple Watch is charged at least 50 per cent and placed on its charging pad before installing the update. (Image:Unsplash)  

Moreover, the company added a security enhancement for Apple Pay. Users can head to the Apple Watch app on their iPhone and head to the 'General & Software Update' section. Make sure the smartwatch has over 50 per cent charge and is charging to start the update. As for some background of the "False Touch" issue, the company had earlier reported that it is investigating the issue of "false touches" on the latest Apple Watches.

Also Read: WatchOS 10.1 Features: Control Your Apple Watch Without Touching The Screen Using 'Double Tap Gesture'; Check Supported Devices Here

This could cause the screen to "jump erratically" or work without any direct interaction, citing the memo, MacRumors reported. The behaviour could include dialling calls and limiting users from entering the passcode. A force restart on an affected device was the short-term remedy recommended in the past.