that's likely the problem then - a compatibility issue with the Esri proxy and
cacheBust parameter that confuses espg.io (and potentially other urls that you do not happen to be accessing)
You might want to consider changing your configuration so the esri proxy is only used for certain domains and not others (like epsg.io). That can be done in
esri/urlUtils. That's generally a good idea overall though I also recognize that it may not be possible /practical in your implementation.
coming soonseveral times in the past and have been wrong so I won't say it now. Sorry I can't be more specific at this time.
@ERS-Long The legend for Feature layers in the layerControl widget isn't a typical legend. The symbols are built from the layer's render when the layerControl is first instantiated. I forget the reasoning behind this approach (I didn't write it).
The first workaround that comes to mind is remove the layer from the layer control and add it again. I'm not sure if this will work since the symbols are built from the layer's renderer and may ignore the layer defs (at least that is how it looks like it will behave based on a quick look at the code).
Second possibility is to rely on the Legend widget. You can add
noLegend: true to the
layerControlOptions for that layer so it doesn't show the Legend in the layerControl widget.