Assigned
Status Update
No update yet.
Comments
iv...@google.com
Thank you for the post.
We have verified and logged this issue internally. Please note that we cannot give you any timelines, but you can star the issue to get notifications.
sr...@gmail.com
Any updates to this issue? It's been open for a while.
as...@google.com
Thank you, we understand that requiring Map ID to use Advanced Marker is confusing. The discussion about this is ongoing internally, but we don't have anything yet to share externally.
al...@gmail.com
Please make this happen. To be forced to switch to cloud styling for simply wanting to implement a basic marker is really unnecessary.
Description
Advanced markers are not available to use without setting a map ID.
googleMap.getMapCapabilities().isAdvancedMarkersAvailable()always returns false if a map ID is not set.I understand the need for map IDs when using features such as cloud styling, but there is no good reason for advanced markers to require a map ID. There is no server side element to advanced markers, not to mention the huge cost of using a map ID over the traditional Mobile Native Dynamic Maps SKU. At first glance it seems like the much needed client side upgrades to the legacy markers are being put behind a completely unnecessary paywall.
Is this intended behaviour? If so could we get some clarification as to why advanced markers require the use of a map ID?
Related issue from Maps JavaScript API: