[SOLVED] Weird problem with images when project published

Help & Support
1

Something strange has happened to this project in which many entities in the world do not render when image textures are in range of the camera, even if the entities using them are disabled. Everything works fine when launching from the editor. It’s only published versions that are problematic.

There are errors being reported in the console that sound like it might be a server error, though builds published a few days ago are still working fine.

The following occurs on initialisation:

Error while loading scene https://s3-eu-west-1.amazonaws.com/apps.playcanvas.com/Dee8PJpy/941500.json: The operation is insecure.
uploadTexture@https://s3-eu-west-1.amazonaws.com/apps.playcanvas.com/Dee8PJpy/playcanvas-stable.min.js:211:3
setTexture@https://s3-eu-west-1.amazonaws.com/apps.playcanvas.com/Dee8PJpy/playcanvas-stable.min.js:216:390
draw@https://s3-eu-west-1.amazonaws.com/apps.playcanvas.com/Dee8PJpy/playcanvas-stable.min.js:219:254
drawInstance@https://s3-eu-west-1.amazonaws.com/apps.playcanvas.com/Dee8PJpy/playcanvas-stable.min.js:488:498
renderForward@https://s3-eu-west-1.amazonaws.com/apps.playcanvas.com/Dee8PJpy/playcanvas-stable.min.js:506:473
renderComposition@https://s3-eu-west-1.amazonaws.com/apps.playcanvas.com/Dee8PJpy/playcanvas-stable.min.js:531:315
render@https://s3-eu-west-1.amazonaws.com/apps.playcanvas.com/Dee8PJpy/playcanvas-stable.min.js:1099:39
c/<@https://s3-eu-west-1.amazonaws.com/apps.playcanvas.com/Dee8PJpy/playcanvas-stable.min.js:1114:499
start@https://s3-eu-west-1.amazonaws.com/apps.playcanvas.com/Dee8PJpy/playcanvas-stable.min.js:1097:451
configure/</</</<@https://s3-eu-west-1.amazonaws.com/apps.playcanvas.com/Dee8PJpy/__start__.js:145:29
e.prototype.loadScene/</<@https://s3-eu-west-1.amazonaws.com/apps.playcanvas.com/Dee8PJpy/playcanvas-stable.min.js:1120:263
_preloadScripts@https://s3-eu-west-1.amazonaws.com/apps.playcanvas.com/Dee8PJpy/playcanvas-stable.min.js:1092:290
e.prototype.loadScene/<@https://s3-eu-west-1.amazonaws.com/apps.playcanvas.com/Dee8PJpy/playcanvas-stable.min.js:1119:393
waitForTemplatesInScene@https://s3-eu-west-1.amazonaws.com/apps.playcanvas.com/Dee8PJpy/playcanvas-stable.min.js:1066:280
load/<@https://s3-eu-west-1.amazonaws.com/apps.playcanvas.com/Dee8PJpy/playcanvas-stable.min.js:1832:780
_onSuccess@https://s3-eu-west-1.amazonaws.com/apps.playcanvas.com/Dee8PJpy/playcanvas-stable.min.js:1034:242
_onReadyStateChange@https://s3-eu-west-1.amazonaws.com/apps.playcanvas.com/Dee8PJpy/playcanvas-stable.min.js:1033:101
request/k.onreadystatechange<@https://s3-eu-west-1.amazonaws.com/apps.playcanvas.com/Dee8PJpy/playcanvas-stable.min.js:1031:372

This is being reported continuously while the textures are in view:

SecurityError: The operation is insecure.
uploadTexture https://s3-eu-west-1.amazonaws.com/apps.playcanvas.com/Dee8PJpy/playcanvas-stable.min.js:211
setTexture https://s3-eu-west-1.amazonaws.com/apps.playcanvas.com/Dee8PJpy/playcanvas-stable.min.js:216
draw https://s3-eu-west-1.amazonaws.com/apps.playcanvas.com/Dee8PJpy/playcanvas-stable.min.js:219
drawInstance https://s3-eu-west-1.amazonaws.com/apps.playcanvas.com/Dee8PJpy/playcanvas-stable.min.js:488
renderForward https://s3-eu-west-1.amazonaws.com/apps.playcanvas.com/Dee8PJpy/playcanvas-stable.min.js:506
renderComposition https://s3-eu-west-1.amazonaws.com/apps.playcanvas.com/Dee8PJpy/playcanvas-stable.min.js:531
render https://s3-eu-west-1.amazonaws.com/apps.playcanvas.com/Dee8PJpy/playcanvas-stable.min.js:1099
c https://s3-eu-west-1.amazonaws.com/apps.playcanvas.com/Dee8PJpy/playcanvas-stable.min.js:1114

Current build minus some recent changes that are apparently not part of the problem: https://playcanv.as/b/Dee8PJpy/

2

Sorry about this :(. This is due to the recent 1.28.4 release. We are working on the fix as I post for 1.28.5. Hang tight!

3

Ah, that’s alright then. At least I haven’t broken something major in the project. In the meantime I’ll export and self-host if necessary.

4

We have now published 1.28.6 which should solve your issue now :slight_smile: Thank you for your patience!

5

Awesome. Can confirm everything is back to normal again.