Search Issue Tracker
Won't Fix
Votes
0
Found in [Package]
1.1.10, 1.5.0
Issue ID
1202583
Regression
No
[Addressable] Sprite's Texture is not included in the bundle when using "Use Existing Build" build mode
How to reproduce:
1. Open the attached project ("case_1202583-addressables-sprite-bug-repro.zip")
2. Open the repro scene ("addressable-sprite")
3. Build Player Content using "Existing Build" mode
4. Enter Play Mode
Expected results: The sprite is loaded and can be seen on the white cube
Actual results: The sprite is loaded but cube remains white because it lacks a texture
Reproducible with: 2018.4.15f1, 2019.2.17f1, 2019.3.0f4, 2020.1.0a18
Couldn't test with 2017.4 (no package manager)
Reproducible with package versions: 1.1.10, 1.5.0
Notes:
1. The issue does not reproduce when "Asset Database" or "Simulate Groups" build modes are used
2. Reproduces only when the sprite's "spritePackingTag" is set to a non-null value, and the sprite is not part of an atlas
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [RayTracing] Impossible to identify individual instances added using RTAS.AddInstances in a compute shader when using ray queries.
- [Linux] "Error: Attempting to resolve render surface with no resolve target specified." error is thrown after creating a Mixed Reality or VR Multiplayer template project
- [Android] The Input on the UI is not decoupled from the frame rate when using the "OnDemandRendering" method
- It is not possible to hide the toolbar of the Game window when observed in 2022.2 or later streams
- WebGPU error When over 2GB memory consumption
Resolution Note:
Issue is caused by sprites having unused "spritePackingTag" tag. These tags should be removed from problematic sprites in order to resolve the issue. It is recommended that users remove tags if they are not in use.