iOS Simulator: Tapping an MKMapView inside a UITableViewCell throws an NSException

Originator:tangphillip
Number:rdar://15429762 Date Originated:11/8/2013
Status:Closed Resolved:
Product:Developer Tools Product Version:Xcode Version 5.0.1 (5A2053)
Classification:Other Bug Reproducible:Always
 
Summary:
If you embed an MKMapView in a UITableView Cell, then tap the cell in the simulator, it'll throw an exception. If you tap the cell on device, there is no exception.

Steps to Reproduce:
See attached test project.

Expected Results:
There should not be an exception, and in fact, there is not one on device.

Actual Results:
The simulator throws an exception, and if you read the data out of it, you get this exception on a subview of MKMapView:

(lldb) register read eax
     eax = 0x15697110
(lldb) po 0x15697110
[<UIView 0xd6d4310> valueForUndefinedKey:]: this class is not key value coding-compliant for the key _annotationContainer.
(lldb) po [0x15697110 userInfo]
{
    NSTargetObjectUserInfoKey = "<UIView: 0xd6d4310; frame = (0 0; 320 100); autoresizesSubviews = NO; gestureRecognizers = <NSArray: 0x15642130>; layer = <CALayer: 0xd6f73d0>>";
    NSUnknownUserInfoKey = "_annotationContainer";
}
(lldb) po 0xd6d4310
<UIView: 0xd6d4310; frame = (0 0; 320 100); autoresizesSubviews = NO; gestureRecognizers = <NSArray: 0x15642130>; layer = <CALayer: 0xd6f73d0>>
(lldb) po [0xd6d4310 superview]
<MKMapView: 0x13b1bf70; frame = (0 105.5; 320 100); clipsToBounds = YES; autoresize = RM+TM; layer = <CALayer: 0xd6e8160>>

Version:
OS X Version 10.9 (13A603)
Xcode Version 5.0.1 (5A2053)
iOS Simulator Version 7.0 (463.9.4)
iOS Version 7.0.3 (11B508)

Notes:


Configuration:


Attachments:
'MapViewException.zip' was successfully uploaded: http://tangphillip.com/openradar/MapViewException.zip

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!