Order of initialization of annotation managers matters!

[androideveloper]

I have found a weird bug! When you initialize symbol manager and the circle manager, your symbol can't be dragged! If you change the order of initialization it works!

Steps to reproduce

Demo https://www.dropbox.com/s/ympu7zg722vehty/MapboxSymbolDragDemo.zip?dl=0

Try to change order of initialization:
symbolManager = SymbolManager(mapView, mapboxMap, style)
circleManager = CircleManager(mapView, mapboxMap, style)

Expected behavior

Symbol should be draggable in any case

Actual behavior

Symbol is draggable only, if circle manager initialized first

Configuration

Android versions: 9.0
Device models: Xiaomi mi 2 lite
Mapbox SDK versions: 7.2.0, plugin-annotation-v7:0.5.0

[LukasPaczos]

This is an interesting case, thanks for the report @androideveloper.

Because we are using mapView.setOnTouchListener() to intercept touch events, only the last created manager will have draggable annotations.

There seem to be 2 ways of resolving this:

• make DraggableAnnotationController a singleton that dispatches drag events to all managers
• expose a way to intercept map touch events before they are passed to the internal gestures manager. This would also resolve mapView.setOnTouchListener#onTouch is not invoked with Annotations #884 as we wouldn't have to rely on the OnTouchListener.

Will update this ticket with progress, if we find any of above viable.

[androideveloper]

@LukasPaczos Thanks for the update! I will keep it as the last created manager until this is resolved.

[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.

[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.

[stale]

Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward?

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

[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.

[adrianababakanian]

We should re-open this, since recent reports on Stack Overflow indicate that developers are still encountering the issue.