Actual Result:
- After showPicker(for:), the system AccessorySetupUI RemoteAlert brings up a remote keyboard.
- User taps are dispatched to AccessorySetupUI’s UIRemoteKeyboardWindow instead of the picker content window.
- App-side endEditing(true) / resignFirstResponder cannot dismiss it because the keyboard belongs to the system AccessorySetupUI remote scene.
Key Evidence:
- 19:51:54.066: App window snapshot before showPicker has no UITextEffectsWindow.
- 19:51:54.009968: ASAccessorySession ### showPickerWithDisplayItems
- 19:51:54.013299: AccessorySetupUI showPickerWithOverrideBundleID
- 19:51:54.051591: AccessorySetupUI reports remote keyboard onscreen, frame {{0, 623}, {440, 333}}
- 19:51:54.095643: display layout shows com.apple.AccessorySetupUI foreground and com.osmo.tech obscured.
- 19:51:56.207/19:51:56.305: touch events are sent to <UIRemoteKeyboardWindow> and logged as KeyboardTouch touch down/up.
Questions for Apple:
- Is AccessorySetupKit picker expected to show a keyboard when no text input is focused?
- Is it a system bug that UIRemoteKeyboardWindow covers/intercepts the “Find Accessories” action?
- Is there any public API for a third-party app to dismiss the keyboard inside AccessorySetupUI RemoteAlert?
- If this is expected behavior, what is the recommended workaround or required picker/display item configuration?
