# Bing Map Tile Issue - No Code Change **URL:** \ **Category:** CesiumJS\ **Created:** [July 12, 2019, 8:13am UTC](https://community.cesium.com/t/bing-map-tile-issue-no-code-change/8454 "2019-07-12T08:13:14Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![josh3](https://sea2.discourse-cdn.com/cesium/user_avatar/community.cesium.com/josh3/32/1987_2.png) [@josh3](https://community.cesium.com/u/josh3)\ **Post date:** [July 12, 2019, 8:13am UTC](https://community.cesium.com/t/bing-map-tile-issue-no-code-change/8454/1 "2019-07-12T08:13:14Z")
1. A concise explanation of the problem you're experiencing. We are suddenly experiencing an issue where Bing Map tiles fail to load completely in Safari, and load partially in Chrome. Our bing map tile URLs look like this, and throw a warning when opened in a browser, NET::ERR\_CERT\_COMMON\_NAME\_INVALID [https://ak.dynamic.t3.tiles.virtualearth.net/comp/ch/311230132102303020?mkt=en-US&it=G%2CL&shading=hill&og=426&n=z](https://ak.dynamic.t3.tiles.virtualearth.net/comp/ch/311230132102303020?mkt=en-US&it=G%2CL&shading=hill&og=426&n=z) I checked a basic example in the sandcastle, and the tile URLs for the same style map look like ![](https://global.discourse-cdn.com/cesium/original/3X/7/d/7d33c8fc62133229a744324c8751e578810943aa.jpeg) These do not have the same issue as above. I tested our access tokens in a sandcastle, and they work fine. This issue causes Chrome to throw a not secure warning on our application, due to active content with certificate errors. 4. The Cesium version you're using, your operating system and browser. 1.57 ![Screen Shot 2019-07-12 at 6.12.07 pm.png](https://global.discourse-cdn.com/cesium/original/3X/e/b/eb73b813138158a7dd57abbd5d4a78d605c1e1b7.png) ---
**Author:** ![Kevin\_Ring](https://sea2.discourse-cdn.com/cesium/user_avatar/community.cesium.com/kevin_ring/32/2003_2.png) [@Kevin\_Ring](https://community.cesium.com/u/Kevin_Ring)\ **Post date:** [July 12, 2019, 11:23am UTC](https://community.cesium.com/t/bing-map-tile-issue-no-code-change/8454/2 "2019-07-12T11:23:41Z")
This sounds like [https://github.com/AnalyticalGraphicsInc/cesium/pull/7861](https://github.com/AnalyticalGraphicsInc/cesium/pull/7861), which was fixed in Cesium v1.58. When we fixed it, the problem only affected Bing’s new “on demand” layers, but it’s likely something changed on the Bing side to make the problem more widespread. ---
**Author:** ![omar](https://sea2.discourse-cdn.com/cesium/user_avatar/community.cesium.com/omar/32/1999_2.png) [@omar](https://community.cesium.com/u/omar)\ **Post date:** [July 12, 2019, 4:03pm UTC](https://community.cesium.com/t/bing-map-tile-issue-no-code-change/8454/3 "2019-07-12T16:03:52Z")
We did just change the Bing API urls that Cesium ion serves, which I think is why it suddenly broke ([https://cesium.com/ion/changelog#2019-07-10](https://cesium.com/ion/changelog#2019-07-10)). Josh, are you able to update to the latest CesiumJS version and confirm that it fixes your issue? ---
**Author:** ![Kevin\_Ring](https://sea2.discourse-cdn.com/cesium/user_avatar/community.cesium.com/kevin_ring/32/2003_2.png) [@Kevin\_Ring](https://community.cesium.com/u/Kevin_Ring)\ **Post date:** [July 13, 2019, 1:02am UTC](https://community.cesium.com/t/bing-map-tile-issue-no-code-change/8454/4 "2019-07-13T01:02:16Z")
Oh ok that makes sense. But it’s probably breaking everyone using a pre-1.58 version of Cesium. Probably worth coming up with a way to avoid that. Off the top of my head, maybe you can either serve the old layers to pre-1.58 version of Cesium (if you know the Cesium version), or you can tell the client to always ask for https? ---
**Author:** ![josh3](https://sea2.discourse-cdn.com/cesium/user_avatar/community.cesium.com/josh3/32/1987_2.png) [@josh3](https://community.cesium.com/u/josh3)\ **Post date:** [July 13, 2019, 4:35am UTC](https://community.cesium.com/t/bing-map-tile-issue-no-code-change/8454/5 "2019-07-13T04:35:33Z")
Hi Omar, confirming that upgrading Cesium to 1.59 fixed the issue. I assume this will effect others and many won't be in a position to upgrade immediately like we were. Might be worth investigating an alternative solution for those effected?