Search Issue Tracker
Won't Fix
Won't Fix in 2023.3.X
Votes
1
Found in
2021.3.0f1
2022.1.3f1
2022.2.0a11
2023.1.0a1
2023.2.0a1
2023.3.0a3
Issue ID
UUM-3697
Regression
No
[UIToolkit] PointerEnterEvent is not registered after being called simultaneously by multiple buttons
Reproduction steps:
1. Download and open the attached "UIToolkit Bug.zip" project
2. Build and deploy the project to iOS
3. Press and hold the left button on the left side of the screen
4. Tap the button on the right side of the screen
5. Release and tap the button on the left side of the screen
Expected result: The button on the left side of the screen displays "ON"
Actual result: The button on the left side of the screen displays "OFF"
Reproducible with: 2019.4.31f1, 2020.3.20f1, 2021.1.24f1, 2021.2.0b14, 2022.1.0a11
Reproduced with: iPhone 12 Pro (iOS 14.2.1), iPhone 6S (iOS 13.3.1)
Reproduced on:
----------, 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
VLNQA00078, Motorola Nexus 6 (Nexus 6), Android 7.1.1, CPU: Snapdragon 805 APQ8084AB, GPU: Adreno (TM) 420,
Windows Touchscreen
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note:
Thanks for the report. This is a known limitation that we currently do not plan to improve in older versions of Unity. This should be addressed in an upcoming version of Unity.
Resolution Note (2023.3.X):
Thanks for the report. This is a known limitation that we currently do not plan to improve in older versions of Unity. This should be addressed in an upcoming version of Unity.