Search Issue Tracker
Won't Fix
Won't Fix in 2021.3.X
Votes
0
Found in
2021.3.30f1
Issue ID
UUM-52667
Regression
No
[AppleTV][UIToolkit] UI navigation gets stuck when selecting a Text Field
How to reproduce:
1. Open the attached Project "textFieldTest"
2. Build and Run the Scene "New Scene" on an Apple TV device
3. In the Player, use the Apple TV Remote to navigate to the Text Field
4. Attempt to navigate to the Button
Expected result: The Text Field loses focus and the Button becomes focused
Actual result: The Text Field remains focused
Reproducible with: 2021.3.30f1, 2022.2.0b15
Fixed in: 2022.2.0b16
Reproduced on:
- Apple TV 4K 1st Generation (tvOS 14.3)
Notes:
- Does not reproduce with TMP Input Fields
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
- Required SpriteMask class (ID 331) is stripped when "Strip Engine Code" is enabled
- “Maximized serialized file backup not found” error is thrown when minimizing a window in a newly opened project
- Build stack trace contains invalid lines when building with IL2CPP using scripts with delegates containing generic types in the signature
- Entities Systems window has a “Show Full Player Loop” dropdown which does nothing when clicked after enabling “Show Full Player Loop”
- Entities Hierarchy Search “Show/Hide” button’s Lens Icon is blurry when the Editor is on an external monitor
Resolution Note:
Thank you for bringing this issue to our attention. After careful consideration, we have determined that other higher-priority issues should take precedence, and we have decided not to address your issue at this time. The priority level is determined by factors such as the severity and frequency of an issue and the number of users affected by it.
In this specific case, the work done to support touch screen keyboard should have addressed this. Unfortunately, due to the nature of the work (which includes a refactor on the TextField in addition to other miscellaneous adjustments done to the focus), it is considered too complex and risky to backport to 21.3. We appreciate your input and understanding, and please let us know if you have any other concerns or issues you would like to report in the future.
Resolution Note (2021.3.X):
Thank you for bringing this issue to our attention. After careful consideration, we have determined that other higher-priority issues should take precedence, and we have decided not to address your issue at this time. The priority level is determined by factors such as the severity and frequency of an issue and the number of users affected by it.
In this specific case, the work done to support touch screen keyboard should have addressed this. Unfortunately, due to the nature of the work (which includes a refactor on the TextField in addition to other miscellaneous adjustments done to the focus), it is considered too complex and risky to backport to 21.3. We appreciate your input and understanding, and please let us know if you have any other concerns or issues you would like to report in the future.