Non Addressable SpriteAtlas loading inconsistencies

[chrismarch_1]

My project is using Addressable sprite textures, with non Addressable SpriteAtlases. This works fine when we load the atlased sprites by address string for their individual sprite textures (the sprite atlas is loaded and not the individual texture, as desired), but when we use an AssetReference with the GUID of the sprite texture2d and subobject name the sprite name, then the individual sprite texture is loaded under iOS, and if those sprite textures are in a spriteatlas, the textures do not render under iOS (although in the editor, they are fine with the various playmode scripts)

How does the case work when we load the spriteatlas using the individual sprite texture address string, and how can we make the assetreference case work this way? We believe we are following this supported case, in the 1.16 docs:

Addressable Sprite Example 2: The three textures in Example 1 are put into a SpriteAtlas. That atlas is not Addressable. One of the AssetBundles generated contains that atlas texture and is about 1500KB. The other two AssetBundles only contain Sprite metadata (a few KB), and list the atlas AssetBundle as a dependency. Which AssetBundle contains the texture is deterministic in that it is the same through rebuilds, but is not something that can be set by the user. This is the key portion that goes against the standard duplication of dependencies. The sprites are dependent on the SpriteAtlas texture to load, and yet that texture is not built into all three AssetBundles, but is instead built only into one.

(Unity 2019.4.10f1, Addressables 1.16.1)

[Treyrannosaurus-Rex]

Hello Chris! Let me kick this over to the team, and see if maybe the Documentation needs updated or if they have any guidance to share.