In iOS 16 the three-finger gesture bug returns

In iOS 16 the three-finger gesture bug returns. Some game developers are warning players not to upgrade to iOS 16 due to a bug with the system’s three-finger gesture, which affects gameplay. The problem is that the triple-touch gesture to reveal the undo / cut / copy / paste menu, as well as the three-finger swipe gesture to undo or redo the last action, are a little too zealous in iOS 16, activating in contexts where they shouldn’t.

How to recover deleted SMS or iMessage on iPhone?

Most regular apps work fine, as they only rely on one-finger interactions. But games and apps that require the user to perform multi-touch gestures, such as in rhythmic games or virtual instrument apps for creating music – are more affected, as 9to5Mac points out, as three-finger gestures open the menu. change, and interfere with app experiences.

This is a familiar bug, as a very similar problem surfaced at the launch of iOS 13, when the triple-tap menu was first added. Apple quickly changed it so that three-finger gestures wouldn’t trigger in situations where the user was unlikely to want to initiate such actions, such as in a full-screen game.

These precautions seem to have been lost with iOS 16. The problem also occurs in system apps. For example, opening the Camera app and pinching three fingers on the screen to zoom in or out, will in most cases cause iOS 16 to activate the undo / cut / copy / paste system menu. The same behavior can be replicated in Safari, Settings, and most other Apple apps.

It happens sometimes – but not always – in GarageBand when playing chords on the virtual keyboard. Furthermore, the bug manifests itself in a multitude of games. It just depends on whether the gameplay requires three-finger interactions. This explains why most developers urge users not to upgrade, especially if they want to keep playing rhythm games.

Obviously, this is a bug that Apple can easily solve by simply applying the same strategies in force in iOS 15. At the moment, Apple has not yet officially recognized the problem, which also occurs on the iOS 16.1 beta.

Leave a Reply