Copyright © 2026 Unity Technologies
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.
How to reproduce:
Actual result: The cube doesn’t move after the touch of the screen and console doesn’t print where the screen was touched
Expected result: The cube moves after the touch of the device screen and the console print where the screen was touched
Reproducible with: 6000.5.0a5, 6000.6.4f1, 6000.7.0b3, 7000.0.0a1
Not reproducible with: 6000.0.84f1, 6000.3.25f1, 6000.5.0a4
Built with: Windows 11, macOS 26.6.2
Reproducible with these devices:
VLNQA00667 - Google Pixel 10 Pro Fold (Pixel 10 Pro Fold) - CPU: Tensor G5, GPU: PowerVR D-Series DXT-48-1536, OS: 16
VLNQA00663 - Samsung Galaxy S26 Ultra (SM-S948B) - CPU: Snapdragon 8 Elite Gen 5 (SM8850), GPU: Adreno 840, OS: 16
VLNQA00662 - Samsung Galaxy S26+ (SM-S947B) - CPU: Exynos 2600, GPU: Xclipse 960, OS: 16
VLNQA00642 - Google Pixel 9a (Pixel 9a) - CPU: Google Tensor G4, GPU: Mali-G715, OS: 15
VLNQA00625 - iPhone 16 Pro Max (MYWX3QN/A) - CPU: Apple A18 Pro, OS: 18.3.1
VLNQA00539 - iPhone 12 Pro (MGMM3ET/A) - CPU: Apple A14 Bionic, OS: 16.5.1
VLNQA00319 - Google Pixel 4 (Pixel 4) - CPU: Snapdragon 855 SM8150, GPU: Adreno 640, OS: 13
Notes:
Issues you vote on will appear here