You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 8, 2023. It is now read-only.
Pretty sure this is expected behavior. queryPointAnnotations relies on queryRenderedFeatures, and a point annotation isn't rendered until it has a chance to pass through the worker layout step, which is an asynchronous operation.
Thank you for the explanation, makes sense that the marker will not show up until they are actually rendered. I'm converting this issue to an android-docs issue.
And the returned View wouldn't be null if the MarkerView was found in the current Viewport. With above described behavior the user needs to wait since adding one is a asynchronous operation. To make this easier for integrating I'm providing an additional addMarker method with a callback interface that is invoked when getView() wouldn't return null anymore. This would end up in using an API as:
When looking into #7072, I noticed that a recently added point annotation isn't returned as a result of queryPointAnnotations.
What I do is add a point annotation to the map and almost immediately execute a query with:
This currently results in returning 0 annotations,
if I delay this action this results in returning 1 annotation.
cc @brunoabinader
The text was updated successfully, but these errors were encountered: