Search Issue Tracker
Won't Fix
Won't Fix in 2023.3.X
Votes
0
Found in
2023.2.0a1
2023.3.0a3
Issue ID
UUM-24877
Regression
No
[Android] Hide Mobile Input blocking input events when enabled
1. Open the user’s attached project
2. Build and run the project for Android
3. Tap on the large white Input Field to open the Mobile Keyboard
4. Tap on the “Submit” button
5. Observe the result
Expected result: The “Submit” button registers the input and the counter of “Submit Clicked” goes up by 1
Actual result: The input is not registered and the counter is left unchanged
Reproducible with: 3.0.6 (2020.3.37f1, 2021.3.7f1), 3.2.0-pre.3 (2022.1.11f1, 2022.2.0b2, 2023.1.0a5) 4.0.0-pre.1 (2022.1.11f1, 2022.2.0b2)
Can’t test with: 4.0.0-pre.1 (2023.1.0a5 - TMP error)
Reproduces with these devices:
VLNQA00122 - Samsung Galaxy S9 (SM-G960F), CPU: Exynos 9 Series 9810, GPU: Mali-G72, OS: 10.0.0
VLNQA00293 - OPPO R17 Pro (PBDM00), CPU: Snapdragon 710 SDM710, GPU: Adreno 616, OS: 9.0.0
VLNQA00263 - Google Pixel 3 (Pixel 3), CPU: Snapdragon 845, GPU: Adreno 630, OS: 12.0.0
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:
Thank you for bringing this issue to our attention. Unfortunately, after careful consideration, we will not be addressing your issue at this time, as we are committed to resolving other higher-priority issues and delivering the new UI system. Our priority levels are determined by factors such as the severity and frequency of an issue and the number of users affected by it. However, we know each case is different, so please continue to log any issues you find and provide any general feedback on our roadmap page to help us prioritize.
Forum announcement
https://forum.unity.com/threads/ui-toolkit-update-q3-2022.1329159/
Roadmap https://unity.com/roadmap/unity-platform/ui
Resolution Note (2023.3.X):
Thank you for bringing this issue to our attention. Unfortunately, after careful consideration, we will not be addressing your issue at this time, as we are committed to resolving other higher-priority issues and delivering the new UI system. Our priority levels are determined by factors such as the severity and frequency of an issue and the number of users affected by it. However, we know each case is different, so please continue to log any issues you find and provide any general feedback on our roadmap page to help us prioritize.
Forum announcement
https://forum.unity.com/threads/ui-toolkit-update-q3-2022.1329159/
Roadmap https://unity.com/roadmap/unity-platform/ui