Search Issue Tracker

Fixed in 2022.1.X

Fixed in 2019.4.X, 2020.3.X, 2021.1.X, 2021.2.X



Found in






Issue ID




[Android] [InputSystem] Callback is not called for multiple touches after tapping the screen rapidly for about 2 seconds



Steps to reproduce:
1. Open the attached project ""
2. Build and run the "SampleScene" Scene
3. Rapidly click the screen using multiple fingers for 2-3 seconds
4. Touch the screen with one finger, then without releasing it with another, and so on until you reach 6 fingers all touching the screen at the same time

Expected results: cube on the screen turns green and goes back to white after each touch
Actual result: cube on the screen turns green and goes back to white after the first touch but not after any sequential touches

Reproducible with: 2019.4.27f1 (1.0.0-preview, 1.0.2), 2020.3.3f1 (1.0.2), 2021.1.8f1 (1.0.2), 2021.2.0a18 (1.0.2, 1.1.0-preview.3)
Could not test with: 2018.4.35f1 - project throws errors when trying to downgrade to Input System 0.9.6-preview or older

Reproducible on:
VLNQA00317, Vivo V1924A (V1924A), Android 9, CPU: Snapdragon 855 SM8150, GPU: Adreno (TM) 640
HTC U11 (Android 9) - according to the user
Xiaomi Redmi Note 9 Pro (Android 10) - according to the user
Samsung Galaxy S8 (Android 9) - according to the user

Does not reproduce on:
iPhone 12 (iOS 14.1)
iPad Pro 12.9 1st gen (iOS 13.4.1)
VLNQA00277, Asus ROG Phone, Android: 8.1.0, CPU: Snapdragon 845 SDM845, GPU: Adreno (TM) 630
VLNQA00006, Samsung Galaxy S7, Android: 8.0.0, CPU: Exynos 8 Octa 8890, GPU: Mali-T880
VLNQA00121, Samsung Galaxy S9, Android: 9, CPU: Exynos 9 Series 9810, GPU: Mali-G72
VLNQA00313, Huawei Y6 Ⅱ Compact (HUAWEI LYO-L01), Android 5.1, CPU: MediaTek MT6735, GPU: Mali-T720
VLNQA00294, Oppo Reno Z 中国版 (PCDM10), Android 9, CPU: Mediatek MT6779 Helio P90, GPU: PowerVR Rogue GM9446
VLNQA00286, Meizu - (PRO 5), Android 7.0, CPU: Exynos 7 Octa 7420, GPU: Mali-T760
VLNQA00335, Samsung Galaxy S20 5G (SM-G986B), Android 10, CPU: Exynos 990, GPU: Mali-G77
----------, Huawei - (ELS-NX9), Android 10, CPU: NOT FOUND, GPU: Mali-G76
VLNQA00264, Samsung Galaxy S10+ (SM-G975F), Android 10, CPU: NOT FOUND, GPU: Mali-G76
VLNQA00279, Samsung Galaxy S10+ (SM-G975U), Android 9, CPU: Snapdragon 855 SM8150, GPU: Adreno (TM) 640
VLNQA00288, Samsung Galaxy J7 (SM-J730F), Android 8.1.0, CPU: Exynos 7 Octa 7870, GPU: Mali-T830
VLNQA00022, Xiaomi Redmi Note 3 (Redmi Note 3), Android 6.0.1, CPU: Snapdragon 617 MSM8952, GPU: Adreno (TM) 510
N/A, Google Pixel 3 XL (Pixel 3 XL), Android 11, CPU: NOT FOUND, GPU: Adreno (TM) 630
N/A, Huawei - (NOH-NX9), Android 10, CPU: NOT FOUND, GPU: Mali-G78
VLNQA00001, Google Pixel 2 (Pixel 2), Android 11, CPU: Snapdragon 835 MSM8998, GPU: Adreno (TM) 540
VLNQA00316, Samsung Galaxy Note10 (SM-N970F), Android 9, CPU: Exynos 9 Series 9825, GPU: Mali-G76

- It may be possible to reproduce the issue on more devices, however, reproduction is more complicated and possibly not as consistent
- Locking & unlocking the device or dragging the notification bar down makes the touch inputs functional again
- Does not reproduce on Windows Standalone (tested using Microsoft Surface Pro 4)

  1. Resolution Note (fix version 2022.1):

    Fixed in version 2022.1.0a4

  2. Resolution Note (fix version 2021.2):

    fixed in 2021.2.0b11

  3. Resolution Note (fix version 2021.1):

    Fixed in version 2021.1.18f1

  4. Resolution Note (fix version 2020.3):

    fixed in 2020.3.18f1

  5. Resolution Note (fix version 2019.4):

    Fixed in version 2019.4.30f1

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.