Cache problem with Scene Layer in AGOL

[MaximeDemers]

Hi,

I have published a Scene Layer to AGOL with Pro 2.7. The scene layer is a multipatch layer of buildings. The buildings are using a simple plain white texture.

I have published the scene layer with the same name of a previous scene layer that I had previously deleted from AGOL.

Now when I open the scene layer in the scene viewer, I still see some of the old scene layer buildings, wich was using an orange texture. Also, some buildings are just missing.

However, if I open the scene layer using the private mode of my browser, the orange buildings are not visible and the scene layer is displayed correctly.

The scene layer in scene viewer (normal browser mode)

The same scene layer in the scene viewer (private browser mode)

I have rebuild the cache of the scene layer but that does not solve the problem. The cache seems to be in the browser.

Is there any solution for this?

Thank you!

[MaximeDemers]

With further research, I have discover that AGOL is caching scene layer geometries locally in the IndexedDB.

The problem however is that they are using the scene layer request url as the primary key wich is not based on the item id but the name of the layer.

That means the solution would be to republish the scene layer under a different name, and never use a name that was previously used if you dont want that kind of problem.

ESRI, should do something about this...

[NicolasGIS]

Hi @MaximeDemers,

Facing the same issue.

What is interesting is that it is not solely the sceneLayer URL but there is also a version in it: /services/BatimentHauteur_MP/SceneServers/layers/0/v19/14 

Not sure if this was supposed to avoid the problem we are facing.

[PhilipMielke]

We've also faced this problem on a larger enterprise application, and it's causing some inconsistent results with our application.  @JeremyBartley @ArnoFiva @JuliePowell 

[NicolasGIS]

Same issue here.

We published it with the same name not to break other applications consumming it but now at small scales we have this kind of artefact for an integratedMeshLayer:

Problem is that clearing the indexedDB is not the kind of workflow you want to tell to your users...