Microsoft Edge will not load a TileLayer

AndrewTerwiel

My map will not load and I get this in the console when using Edge.

<SPAN class="punctuation token">[</SPAN>esri<SPAN class="punctuation token">.</SPAN>layers<SPAN class="punctuation token">.</SPAN>TileLayer<SPAN class="punctuation token">]</SPAN> #<SPAN class="token function">load</SPAN><SPAN class="punctuation token">(</SPAN><SPAN class="punctuation token">)</SPAN> Failed to load layer <SPAN class="punctuation token">(</SPAN>title<SPAN class="punctuation token">:</SPAN> <SPAN class="string token">'Aerial'</SPAN><SPAN class="punctuation token">,</SPAN> id<SPAN class="punctuation token">:</SPAN> <SPAN class="string token">'16be45292c8-layer-0'</SPAN><SPAN class="punctuation token">)</SPAN> <SPAN class="punctuation token">[</SPAN>request<SPAN class="punctuation token">:</SPAN>server<SPAN class="punctuation token">]</SPAN><SPAN class="punctuation token">:</SPAN> Unable to load https<SPAN class="punctuation token">:</SPAN><SPAN class="operator token">/</SPAN><SPAN class="operator token">/</SPAN>maps<SPAN class="punctuation token">.</SPAN>npdc<SPAN class="punctuation token">.</SPAN>govt<SPAN class="punctuation token">.</SPAN>nz<SPAN class="operator token">/</SPAN>arcgis<SPAN class="operator token">/</SPAN>rest<SPAN class="operator token">/</SPAN>services<SPAN class="operator token">/</SPAN>Aerial<SPAN class="operator token">/</SPAN>MapServer<SPAN class="operator token">?</SPAN>f<SPAN class="operator token">=</SPAN>json status<SPAN class="punctuation token">:</SPAN> <SPAN class="number token">0</SPAN>‍<SPAN class="line-numbers-rows"><SPAN>‍</SPAN></SPAN>

I was getting this while using ArcGis JS 3x and so I converted the map to 4x but I still get this error and the map won't load.

AndrewTerwiel

Hi Noah,

I'm using Microsoft Edge 44.17763.1.0, Microsoft EdgeHTML 18.17763. This problem only occurs when the Tilelayer is loaded into a webmap that is not hosted on our web adaptor server. We are currently migrating from ArcGIS 10.3.1 to Enterprise 10.6.1 and I tested this in our new environment with a Tilelayer hosted there and it worked, no problems at all. Please don't do any more investigation of this problem, unless you are personally interested, as it appears that it will be resolved once all our services are hosted on 10.6.1.