Customised annotation callout closes automatically when changing the viewport

[pushian]

Platform: iOS
Mapbox SDK version: "https://www.mapbox.com/ios-sdk/Mapbox-iOS-SDK.json" ~> 3.7

Steps to trigger behavior

1. Tap on the annotation
2. The customised callout view will appear
3. Move the map slightly a bit and the callout view will disappear

Expected behavior

The callout view should remain when the map is moving and should only be dismissed when the map is tapped somewhere else

Actual behavior

Move the map slightly a bit and the callout view will disappear

[pushian]

Hi @frederoni, I have gone through all the relevant issues and found this issue should have been fixed in the issue #6676 but I am still seeing it happening. Please advise.

[frederoni]

The MGLCalloutView protocol provides an optional dismissesAutomatically property. Is this property implemented in your concrete class and set to NO?

[pushian]

@frederoni thanks for the information and I have tried to set as following:
class CustomCalloutView: UIView, MGLCalloutView { var dismissesAutomatically = false }
It is working that the callout view will now remain when I am changing the viewport but the callout view is not moving together with the viewport. Is there any other settings that I have to implement to make the callout view moving also?

[pushian]

I tried to implement the variable isAnchoredToAnnotation but it resulted in a very strange behaviour. Each time I click on one of the annotation, the callout view will always appear at the top left corner of the screen (check out the gif I have uploaded).
All the markers on the map are displayed using Features and Layers. I am using the following code to show the callout view:
func showCallout(feature: MGLPointFeature) {
let point = MGLPointFeature()
point.title = feature.attributes["name"] as? String
point.coordinate = feature.coordinate
mapView.selectAnnotation(point, animated: true)
}

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[julianrex]

Believe this is likely fixed in recent changes, however we should re-test.

[stale]

This issue has been automatically detected as stale because it has not had recent activity and will be archived. Thank you for your contributions.