Basemap Map tool shows double custom basemaps

[DavidColey]

Hello - The basemap tool in the Experience Builder map tools now shows custom basemaps in the basemap gallery twice when a custom basemap is used as the webmaps basemap. 

When a custom basemap is not used as the webmap basemap, for example the Streets or Topo, this is not an issue.

To see what I mean you will see the "Sarasota County Local (Vector)" basemap twice:

https://experience.arcgis.com/experience/36f63bf761e4483b9e89120efe8ed860

The webmaps in this app use a custom localize basemap with some vector tile layers.  When the user opens the basemap tool, this custom local basemap appears twice.

I am not seeing my custom local basemaps twice in my AGOL custom basemap group, the webmap count making up the basemaps show as expected, i.e there are no duplicate webmaps.  The AGOL custom basemap group does however participate in a distributed collaboration, where I send the custom vector tile layers to the group by reference from our guest Enterprise Portal.

Thanks-

@Jianxia 

[SubodhDhakal_NZTA]

We have come across this exact issue and wanting some clarification from Esri dev team. Any updates here how we can mitigate this ? 

[DavidColey]

not from me, the last feedback I received was from @TonghuiMing last month.  It's not something that is fixing itself on its own, apparently.

[DanielWebb · Accepted solution]

I don’t know if this will help, but we also kept getting a duplicate basemap in the gallery. We have some custom imagery that is layered on top of the Esri World imagery, so in the web map we added a visibility range to our imagery so as not to show until zoomed in. This created a duplicate basemap in the basemap gallery. When we removed that visibility range, the duplicate also disappeared in the gallery. So ExB must create a weird duplicate simply by customizing the properties by web map? I don't know. It's definitely an Esri thing on the backend or something.

I don’t know if this helps your situation. Figured I’d just let you know what worked for us.

[DavidColey]

Yeah that did work, thanks for this @DanielWebb  Yes it has to do with the visibility scales.  Although I am using the standard web mercator visibility scales for the vector tile layers that I include as part of my custom webmap basemaps, I am not using all levels that are present in the default world topo or world imagery. i.e levels 0 - 21, I'm like at 15-20 or 13-21 depending.

But regardless, re-setting the visibility scales to all be World - Room in my webmap-basemaps, that seems to have done it.