UISearchBar/UISearchDisplayController warnings with VoiceOver

Originator:greg
Number:rdar://15245398 Date Originated:10/16/2013
Status:Open Resolved:
Product:iOS Product Version:7
Classification:UI/Usability Reproducible:Always
 
Summary:
Numerous warnings are printed to the console when using a standard UISearchDisplayController with VoiceOver.

Steps to Reproduce:
1. Set up a basic UISearchDisplayController project (attached).
2. Turn on voiceover and run
3. Select the search bar.
4. View console

Expected Results:
Empty console

Actual Results:
2013-10-16 17:32:57.712 ScopeBarBugPhone[9309:60b] |warning| **** Accessibility: Could not find a valid index for <UISearchDisplayControllerContainerView: 0x16dac340; frame = (0 -20; 320 568); autoresize = W+H; layer = <CALayer: 0x16dbad90>> in -[UITableView indexOfAccessibilityElement:]
2013-10-16 17:32:57.719 ScopeBarBugPhone[9309:60b] |warning| **** Accessibility: Could not find where <UISearchDisplayControllerContainerView: 0x16dac340; frame = (0 -20; 320 568); autoresize = W+H; layer = <CALayer: 0x16dbad90>> starts. Was its parent [<UITableView: 0x1712e600; frame = (0 0; 320 568); clipsToBounds = YES; opaque = NO; autoresize = W+H; gestureRecognizers = <NSArray: 0x16d8d420>; layer = <CALayer: 0x16d8b1a0>; contentOffset: {0, -20}>] set correctly or did it disappear?


Version:
iOS 7

Notes:
Regression since iOS 6?

Configuration:


Attachments:
'ScopeBarBugPhone.zip' was successfully uploaded.

Comments


Please note: Reports posted here will not necessarily be seen by Apple. All problems should be submitted at bugreport.apple.com before they are posted here. Please only post information for Radars that you have filed yourself, and please do not include Apple confidential information in your posts. Thank you!