SpriteAtlas, AssetBundles and 'Include in Build'

[AnthonyReddan]

I’ve seen now in a number of places that ‘Include in Build’ simply means that a Sprite will correctly reference its SpriteAtlas (even if its in an asset bundle), like from here :

The “Include in build” has created some confusion. For this particular situation, this check box need to be checked. Doing so will make sure the sprite will reference to the atlas’s texture in the asset bundle, in this sense, the asset bundle is a “build”

For now, you can check the option “Include in build” to ensure the sprite in the asset bundle will reference to the atlas in the asset bundle.

However, it seems that by checking this box, Unity is including the SpriteAtlas in my aab/apk build. I can see the textures in the build report (taking up 1.8% of the size). Also, the aab/apk size increases when I check this box.

Is this the case or is there something potentially wrong with my setup? We obviously don’t want our SpriteAtlas in the build if they’re in AssetBundles. I know I can do LateBinding but I’m just looking for clarity on how this is actually supposed to function.

[AnthonyReddan]

Managed to figure it out. There were UI prefabs in the build that were referencing Sprites from the atlases. Unity was forced to include them in this case. I’m solving it by implementing a separate script to load SpriteAtlases on demand.