Hi all,
It appears there's been a recent update changing how basemaps are handled, and this has broken the functionality of custom basemaps (produced in Vector Tile Style Editor) in ArcGIS Pro.
I went in today to make a simple custom basemap--just the world topo with no labels at all--then saved it as a tile layer to ArcGIS Online. I then brought the service into ArcGIS Pro, but it does not display the same basemap I'm seeing in Vector Tile Style Editor. Rather, it displays something akin to world street map with labels still on.
When I check the item's source in pro, and in the json, it shows this: https://basemaps.arcgis.com/arcgis/rest/services/World_Basemap_v2/VectorTileServer
Furthermore, past custom basemaps I had made now point to this "World Basemap v2" as well, all rendering incorrectly in ArcGIS Pro. Interestingly, these basemaps still show the proper basemap in ArcGIS Online Map Viewer, they're just broken in ArcGIS Pro.
I've been reading on some recent advancements with Esri's basemap handling, something like consolidation, and I'm thinking this "World Basemap v2" is the source of the problem. Something is wrong with how pro is handling these JSONs, but I'm not adept enough to know what. I'm thinking everything has been consolidated into this "World Basemap v2" layer, and Pro isn't filtering out the topo elements properly, while AGOL is.
This is problematic, as we use custom basemaps quite frequently. Has anybody else encountered this behavior?
