Open Radar

 
Summary:

MKPinAnnotationView states that it is intended to display a pin with an optional drop animation. Unfortunately, however, it is still possible to (mistakenly) associate a custom image with said animation since it inherits from MKAnnotationView. Changing map types when MKPinAnnotationView is used results in the loss of said custom image.

Steps to Reproduce:

1. Extract & run the attached sample project (MapPinAnnotationViews) - a simple UITabBarController with two separate map views. The first tab employs MKAnnotationView to present a custom image on the map. The second tab attempts to apply a custom image to an MKPinAnnotationView.

2. Note that first tab behaves as expected when changing map types. That is to say, the custom image persists.

3. Switch to the second tab - note the appearance of the custom image.

4. Change map types. Note that the red pin replaces the custom image.

Expected Results:

It may be necesssary to modify the inheritance hierarchy or more clearly distinguish the intended use of MKPinAnnotationView & MKAnnotationView in the documentation.

Actual Results:

The pin image appears initially in both cases. Said image remains (as expected) for the MKAnnotationView tab, but it does not for MKPinAnnotationView. In the latter case, the custom image appears, then immediately disappears when changing map types.

Regression:

None.

Notes:

None.