Search Issue Tracker
Won't Fix
Won't Fix in 1.8.X
Votes
0
Found in [Package]
1.8.1
Issue ID
ISXB-867
Regression
No
[AppleTV] Minimal vertical movement is interpreted as vertical swiping when swiping horizontally
How to reproduce:
1. Open the attached Project "AppleTvRemoteNIS.zip" -> AppleTvRemoteNIS
2. Build and Run the Scene "SampleScene" on tvOS
3. Using the AppleTV remote swipe left and right in the build
4. Observe the selection in the Build
Expected result: Only the middle row is selected
Actual result: Even minimal vertical movement causes the selection to jump either up or down
Reproducible with: 1.6.3 (2021.3.37f1), 1.7.0 (2021.3.37f1, 2022.3.25f1, 2023.2.19f1), 1.8.1 (6000.0.0b15)
Reproduced on:
- Apple TV 4K (1st Generation) (tvOS 17.4) + Siri remote (1st Generation)
Notes:
- The user has reported that a plugin (Rewired) works as expected
- Attached in the .zip is a video showing the behavior when swiping left-right
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
- “FMOD failed to set the software format to the custom sample rate…” warnings are thrown as System Sample Rate value is being changed in Audio section of Project Settings window
- VFX Marquee selection does match the visual indicator
- “Invalid AABB aabb” errors are spammed when “Infinity” value is entered in Collider Component fields
- Editor Role does not sync with the MPPM Play Mode Scenario Role when entering Play mode
- Long asset names cause overlap with the “Find” function in search result tabs
Resolution Note:
Thank you for your bug report.
After reviewing the issue the team has decided that this case will be resolved as "Won't Fix". This does not mean that the issue isn’t a legitimate bug, but instead that we are not able to prioritize the fix, at this time.
The case will now be closed, please contact your account manager or PRM if you’d like to discuss this specific case in more detail, or if you would like to provide additional information relating to the severity of this bug.
Resolution Note (1.8.X):
Thank you for your bug report.
After reviewing the issue the team has decided that this case will be resolved as "Won't Fix". This does not mean that the issue isn’t a legitimate bug, but instead that we are not able to prioritize the fix, at this time.
The case will now be closed, please contact your account manager or PRM if you’d like to discuss this specific case in more detail, or if you would like to provide additional information relating to the severity of this bug.