Action buttons can remain visually and functionally pressed after being released. Usually occurs when the player quickly releases the action button, and simultaneously begins a new tap-and-hold gesture elsewhere on the screen (e.g., to move the camera or joystick), leading to unintended continuous actions like mining, placing blocks, or opening containers. Reproduced in “joystick & aim crosshair” mode.
How to Reproduce:
Method A:
1. Set gamemode to survival and hold the destroy action button to break blocks.
2. Quickly release the action button and as the finger lifts, begin a new tap-and-hold gesture elsewhere on the screen. Best done using the claw technique (thumb on buttons, index finger on camera).
Example of method A: "how_to_reproduce.mov"
Method B:
1. Obtain a bow, set gamemode to survival, and hold the interact action button to draw the bow.
2. Quickly release the action button, and as the finger lifts, begin a new tap-and-hold gesture with in the joystick area.
Example of method B: "how_to_reproduce - with_joystick.mov"
Note that in this clip, I have also demonstrated that "elsewhere on the screen" includes the joystick zone when 'Hidden Joystick' is enabled. This suggests that initiating movement via the joystick (especially when using the ‘Hidden Joystick’ setting) can also trigger the bug if it coincides with releasing an action button.
Expected results:
Releasing the action button should always stop the associated action, regardless of what else is happening on the screen.
Observed Results:
The action button remains visually and functionally "pressed" even after the finger is lifted. This leads to unintended continuous actions like mining, placing blocks, or opening containers. The issue only arises when a new touch begins elsewhere on the screen during the release of the action button. It does not occur if the other touch is already active before the release.
Linked issues
is duplicated by 7
MCPE-177042
Attack button is pressed without touching it
Resolved
MCPE-187045
Stuck ui
Resolved
MCPE-191642
Attack button sometimes gets stuck as if being held down when using touch controls.
Resolved
MCPE-203818
Attack button sometimes gets stuck as if being held down when using touch controls.
Resolved
MCPE-217714
Attack Button gets ‘locked’
Resolved
Attachments
Comments 14
migrated
I've attached files of 2 instances where the bug caught me off guard while building up some towers for my base.
Could it be a side-effect of the action buttons' lack of a camera dead zone? Since this bug does not occur for the jump button nor the sneak button.
Can confirm, not only does it occur when using camera right afterwards, but also occurs when using joystick right afterwards (with invisible joystick setting): how_to_reproduce - with_joystick.mov
In an earlier comment, I speculated that the issue might be related to the lack of a camera dead zone for the action buttons, since the bug doesn’t occur with the jump or sneak buttons. However, after further testing, I’ve confirmed that both the jump and sneak buttons function normally- even when used with simultaneous camera or joystick input. So the dead zone theory is likely unrelated.
A more plausible explanation is a multi-touch timing issue: the bug occurs when a new touch begins elsewhere on the screen during the release of an action button. This may cause the release event to be missed or overridden, leaving the button stuck in a "pressed" state.
Based on testing, the affected buttons include:
Destroy (e.g., breaking blocks)
Interact (e.g., placing blocks, drawing a bow, opening containers)
This updated hypothesis better explains the specific timing required to reproduce the bug, and why it doesn’t affect other buttons under the same conditions.
Additional Notes on Unaffected Buttons:
Jump and Sneak (Hold to sneak) correctly stop their action under the same conditions.
Sprint and Sneak (Tap to sneak) are toggle-based so unaffected by release timing.
Pick Block is a one-time action, so even if affected, it would not result in unintended continuous behavior.
This was kinda fixed with 1.21.92 but 1.21.93 hotfix (UI Changelog) reverted back.
This is related to : https://report.bugs.mojang.com/servicedesk/customer/portal/6/MCPE-224290
@floufen No, this is not related to MCPE-224290. That is intentional design from my understanding, and as a side-effect, it may trigger situations where 2 camera inputs at once cause the camera to suddenly snap to a random direction.
THIS bug report is an issue where action buttons could get stuck because the game thinks you are still holding them down, when in reality you were just too quick and are instead moving forward with the joystick, or are just looking around.
@floufen and as for the camera snapping issue, I believe the bug report you are after is MCPE-173571. I hope that directs you to what you’re after.