Search Issue Tracker




Found in



Issue ID




[Android] Touch input is unresponsive when building for Pixel 7 Pro device



How to reproduce:
1. Open the user’s attached ““ project
2. Build and Run for Android
3. Click the “Button“ button

Expected result: Button text changes to “Button pressed 1 times“ and it can be clicked again
Actual result: The button gets stuck in the “pressed” state and can’t be clickedagain

Reproducible with: 2022.2.0a1, 2022.2.3f1, 2023.1.0a26
Not reproducible with: 2020.3.44f1, 2021.3.17f1, 2022.1.0a16

Reproducible with these devices:
Google Pixel 7 (Pixel 7), Android 13, CPU: Google Tensor G2, GPU: Mali-G710

Not reproducible with these devices:
VLNQA00460 - Google Pixel 6 (Pixel 6), CPU: Google Tensor (Whitechapel), GPU: Mali-G78, OS: 13
Huawei - (ELS-NX9), Android 10, CPU: HiSilicon Kirin 990 5G, GPU: Mali-G76
Samsung Galaxy Z Fold2 5G (SM-F916U1), Android 11, CPU: Snapdragon 865 SM8250, GPU: Adreno (TM) 650
VLNQA00494 - iPhone 14 Pro Max, 16.0.3 iOS
VLNQA00358 - iPhone 12, 14.1 iOS
VLNQA00392 - iPad (9th generation), 15.0 iOS

Comments (12)

  1. sacb0y

    Oct 31, 2023 01:40

    Also have this problem with 2022.3.10

    Basically non-samsung devices touch doesn't work.

  2. rytis_unity

    Sep 27, 2023 11:17

    Sorry for the improper fix version. This was fixed in the InputSystem package version 1.6.2.

  3. mikymod_dev

    Sep 26, 2023 10:17

    same issue on 2022.3.5f1 and Pixel 7a. Removing stylus actions does not fix the problem.

  4. KoalityGame

    Jul 10, 2023 16:00

    This bug is still not fixed as of Unity 2022.3.4f1

  5. TieDeveloper

    May 19, 2023 20:03

    I would like to add that this also happens on the Pixel 7a

  6. TieDeveloper

    May 19, 2023 20:02


  7. DrH1gh

    May 16, 2023 08:56

    We have the same problem with PIXEL 7 PRO. On an emty project with 2 UI buttons.
    Unity: 2022.2.18f1

    It works on this deviced:
    Galaxy S21 / S23
    Pixel 3 / 5 / 6 Pro

  8. OlehHalytskyi

    May 08, 2023 08:06

    This probably happens because Input Action action asset that you use has Touch and Pen binding. Pixel device, for some reason, sends Touch and Stylus events. The workaround for this would be either to have the binding <Pointer/press> or remove Pen binding

  9. gschmitz

    Apr 13, 2023 19:57

    Same here

  10. AlimWarDucks

    Apr 11, 2023 11:29

    I'm having the same problem.

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.