AssetManager - Asset destroyed while still referenced

I’m getting some weird messages on app launch and I’m not sure if this is what’s causing me issues (null refs) that I’m not sure how they’re possible.

[AssetManager] Asset destroyed while still referenced: [56e89847-4a48-4b6c-8088-cb56b844653f (has 2 polyspatial refs, is not unity referenced): resource alive: False iid=10274 name=card_highlight type=Sprite
[AssetManager] Asset destroyed while still referenced: [384cc757-d484-401c-9042-a313205a05e4 (has 2 polyspatial refs, is not unity referenced): resource alive: False iid=10262 name=card_placeholder type=Sprite
[AssetManager] Asset destroyed while still referenced: [568df1ae-79b7-4618-8c7d-947268d3735d (has 2 polyspatial refs, is not unity referenced): resource alive: False iid=10266 name=Sprites-Default type=Material
[AssetManager] Asset destroyed while still referenced: [6e3a6786-520f-434d-bd52-1305c83b5dbd (has 52 polyspatial refs, is not unity referenced): resource alive: False iid=10304 name=Card_metallic_smoothness type=Texture2D
[AssetManager] Asset destroyed while still referenced: [e669ba46-e1f2-4c31-8e74-80e124635490 (has 52 polyspatial refs, is not unity referenced): resource alive: False iid=10302 name=Card_normal type=Texture2D
[AssetManager] Asset destroyed while still referenced: [207eca0d-0b77-457b-9675-e6e71e2592f4 (has 2 polyspatial refs, is not unity referenced): resource alive: False iid=10290 name=card_highlight type=Texture2D
[AssetManager] Asset destroyed while still referenced: [435875c0-30e5-4cf9-befc-75eff9d25cbc (has 2 polyspatial refs, is not unity referenced): resource alive: False iid=10288 name=card_placeholder type=Texture2D
[AssetManager] Asset destroyed while still referenced: [2cc42037-b129-4c66-ba27-d360d40df172 (has 1 polyspatial refs, is not unity referenced): resource alive: False iid=10024 name=Plane type=Mesh

Any idea why this happens and how to avoid? I’m using local addressables so it might be related somehow. Cheers

Same here! Help!

are addressables supported on polyspatial?

did deleting Library and restarting work?

They are supported, with the caveat that shader graphs can’t be loaded from addressables/asset bundles; all shader graphs used have to be present in the base build.

I’m not sure offhand, but if it’s possible to reproduce the behavior in a bug report and let us know the incident number (IN-#####), we can take a look.

2 Likes

Has this issue been resolved?

I don’t think so, because we haven’t received a repro case that lets us know why/where it’s happening. If you can submit such a case as a bug report and let us know the incident number (IN-#####), we can look into it.

This happens when unloading a bundle