Yes, we did clear the cache and cookies. Hmm … I don’t think that I can share our app with you because of proprietary imagery that we have purchased. And we’ve found that if we disable our custom imagery, the problem goes away. It appears that something about loading the custom imagery triggers the problem.
The issue that I’m seeing is that, inside of addDrawCommandsForTile, on line 152661:
tileImagery.useWebMercatorT is false
imagery.textureWebMercator appears to be a valid Texture object
imagery.texture is undefined
Because “useWebMercatorT” is false, it uses the undefined imagery.texture instead of the defined imagery.textureWebMercator.
I’m not sure whether the issue is that imagery.texture is undefined or that useWebMercatorT is false. And I’m not sure what could get me in that state. ;o)
There are some missing tiles in our custom imagery (the imagery just covers a small portion of the globe), for which we get errors like:
An error occurred in “WebMapTileServiceImageryProvider”: Failed to obtain image tile X: 1 Y: 1 Level: 1.
That wouldn’t cause an issue, would it? (it didn’t before we upgraded from 1.24 to 1.27)