accessibilityUserInputLabels is working fine with any view I tried this on. Meaning that the control can be toggled with the provided alternative names when using Voice Control. When setting this property on any UIBarButtonItem though, it seems Voice Control ignores the alternative names provided by setting accessibilityUserInputLabels. For comparison, accessibilityLabel works perfectly when set on UIBarButtonItem. Is anyone facing the same issue? Using Xcode 16.0 (16A242) on iOS 18

Hi there! I am working on a tvOS application with a UISearchController. I have a problem when the grid keyboard is selected in the settings (Settings->General->Keyboard Layout). When the search results are focused, I expect the keyboard to slide to the leading edge to let the search results fill all the available width. This is the standard behavior in all Apple applications. But I can't get that behavior. The keyboard will stay when the search results are focused: Missing image. I'll retry to upload it hoping that it will work this time I followed the video Discover search suggestions for Apple TV (the only one I could find where this topic was dealt with) and did everything mentioned: Embed the UISearchController inside a UISearchContainerViewController Set the collection view of the search results controller as the observed one with setContentScrollView in the search results controller (as explained in the doc) In the video, the behavior I expect is mentioned, and it seems that no additional steps are required to obtain it (~ 9'52''): Our keyboard is highly adaptable to various languages and input methods. You should consider this when laying out your search results. Here are a few examples of alternate layouts. For people using IR remotes, we'll display a grid keyboard. While typing, the search results will only occupy some of the screen width, and then they'll slide in to fill the screen when focused. Is there something I am missing? Or is this a bug and I should file a radar? Environment tvOS 15 UIKit The problem exists on the Simulator as well as on the Apple TVs I tested: 4K (2nd generation) and HD Note I could not find a 3rd party application that gets this behavior. All applications using a UISearchController I could try have the same problem.