As identified on the forums, Cesium for Unity (and potentially all cesium-native clients) attempts to load some Ion imagery overlays from the incorrect URLs. For example, for asset 2411391, the request to the Ion endpoint gives:
Based on this information, Cesium for Unity should calculate the URL https://dev.virtualearth.net/REST/v1/Imagery/Metadata/AerialWithLabelsOnDemand?incl=ImageryProviders&key=<key removed>&uriScheme=https, as CesiumJS does. Instead it tries to make a request for the URL http://localhost/REST/v1/Imagery/Metadata/AerialWithLabelsOnDemand?incl=ImageryProviders&key=<key removed>&uriScheme=https, which obviously fails.
As identified on the forums, Cesium for Unity (and potentially all cesium-native clients) attempts to load some Ion imagery overlays from the incorrect URLs. For example, for asset 2411391, the request to the Ion endpoint gives:
Based on this information, Cesium for Unity should calculate the URL
https://dev.virtualearth.net/REST/v1/Imagery/Metadata/AerialWithLabelsOnDemand?incl=ImageryProviders&key=<key removed>&uriScheme=https
, as CesiumJS does. Instead it tries to make a request for the URLhttp://localhost/REST/v1/Imagery/Metadata/AerialWithLabelsOnDemand?incl=ImageryProviders&key=<key removed>&uriScheme=https
, which obviously fails.