Search Issue Tracker
Fixed
Fixed in 2021.3.31f1, 2022.3.10f1, 2023.1.14f1, 2023.2.0b10, 2023.3.0a1, 7000.0.0a1
Votes
0
Found in
2021.3.27f1
2022.3.5f1
2023.1.4f1
2023.2.0a22
2023.3.0a1
7000.0.0a1
Issue ID
UUM-39962
Regression
No
[tvOS 16] No text navigation occurs when using Controller-Driven Text Input
How to reproduce:
1. Run the attached project on an Apple with tvOS 16.
2. Using a controller/gamepad, select the Input field
3. Attempt to navigate on the keyboard with the controller/gamepad.
Expected result: You can navigate along the keyboard with no issues.
(You can see this if you set 'UnityEngine.tvOS.Remote.allowExitToHome' and 'UnityEngine.tvOS.Remote.touchesEnabled' to set to 'false')
Actual result: No keyboard navigation occurs
Reproduced with: 2020.3.43f1
Reproducible with: AppleTV (tvOS 16)
Not reproducible with: AppleTV (tvOS 13.3.1)
Note: Reproduction video attached
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
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
Resolution Note (fix version 2023.2.0b10):
CQA currently does not have access to a suitable tvOS device that could be used to properly verify this fix. As such, this will be closed without proper verification. If anyone is still able to reproduce the issue on versions that should contain the fix, feel free to reopen the issue and/or message me for further testing.
Resolution Note (fix version 2022.3.10f1):
CQA currently does not have access to a suitable tvOS device that could be used to properly verify this fix. As such, this will be closed without proper verification. If anyone is still able to reproduce the issue on versions that should contain the fix, feel free to reopen the issue and/or message me for further testing.