Search Issue Tracker

Won't Fix



Found in [Package]


Issue ID




Custom Input System doesn't recognise touch release on devices with stylus and laptops with a touch screen when the Input Action map has a Position[Pen] action

Package: Input System


How to reproduce:
1. Open the "IN_49292" project
2. Press File → Build And Run
3. In the Player press the "Button" using a stylus and without a stylus

Expected result: button is released and the message "button clicked" is printed
Actual result: button is not released and no message is printed

Reproducible with: 1.6.1 (2021.3.30f1, 2022.3.9f1, 2023.1.13f1, 2023.2.0b9, 2023.3.0a4)

Reproducible on: Windows 10 Pro
Not reproducible on: No other environment tested

Reproducible on these devices:
VLNQA00174, Microsoft Surface 4
VLNQA00169, Surface-3
Surface Duo (user reported)
VLNQA00326, Samsung Galaxy Note10+ (SM-N975W), Android 11, CPU: Snapdragon 855 SM8150, GPU: Adreno (TM) 640

Not reproducible on these devices:
VLNQA00512, Samsung Galaxy S9 (SM-G960F), Android 10, CPU: Exynos 9 (9810), GPU: Mali-G72
VLNQA00120, Google Pixel 2 (Pixel 2), Android 8.1.0, CPU: Snapdragon 835 MSM8998, GPU: Adreno (TM) 540
VLNQA00267, Samsung Galaxy S10+ (SM-G975F), Android 12, CPU: Exynos 9 (9820), GPU: Mali-G76
VLNQA00178, Xiaomi Redmi Note 4 (Redmi Note 4), Android 6.0, CPU: MediaTek Helio X20 MT6797M, GPU: Mali-T880
VLNQA00489, Htc 10 (HTC 10), Android 6.0.1, CPU: Snapdragon 820 MSM8996, GPU: Adreno (TM) 530
VLNQA00273, Vivo V1821BA (V1821A), Android 9, CPU: Snapdragon 845 SDM845, GPU: Adreno (TM) 630

- Not reproducible on the WebGL Platform
- Couldn't test on other package versions because the user has a custom package
- The issue doesn't reproduce on non-custom package
- On Surface Pro 3/4 tablets input is released when using a stylus
- On the Samsung Galaxy Note 10+ the input is released when not using a stylus (the issue is not present if the stylus is in the holder)
- User mentioned he was able to fix this issue by removing "Point/Position[Pen]" in the UI Input Actions map

  1. Resolution Note:

    Thank you for reporting a bug to Unity.

    We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.

    Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.

    NOTE: It seems like the bug is somewhere inside the custom changes made to the package by the user and the problem does not exist in the vanilla Input System package

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.