Search Issue Tracker
Fixed
Fixed in 2023.2.5f1, 2023.3.0a19
Votes
2
Found in
2023.1.19f1
2023.2.0b17
2023.3.0a13
Issue ID
UUM-56410
Regression
Yes
Importing sprite sheet by using ISpriteEditorDataProvider generates broken Sprites
How to reproduce:
1. Open the user-attached project “AutoSlice”
2. Import the user-attached “sprite-sheet” PNG file into the Assets folder
3. Expand the Sprite and observe the slicing
Expected result: The sprites are sliced and named correctly
Actual result: The sprites are not sliced and named correctly
Reproducible with: 2023.1.0a16, 2023.1.19f1, 2023.2.0b17, 2023.3.0a13
Not reproducible with: 2021.3.32f1, 2022.3.13f1, 2023.1.0a15
Reproducible on: Windows 11 Pro, macOS 14.0 (Apple Silicon) (User reported)
Workaround: Right-click on the sprite asset → Reimport. After that, the sprite is sliced correctly. (Works only with the 2021.3.18f1 and below)
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
- Search field in UI Builder's Library has no character limit
- Changing the value in UI Builder by dragging increases it by a few thousand points when reaching the borders of the screen
- ARM64 architecture DLL incorrectly copied instead of x64 when building for Windows x64
- Crash on TypeTreeIterator::GetNode when opening a specific folder
- Crash on WriteSerializedAssetsV2 when (re)entering the Play Mode in a specific project when IEnumerator Start() is used
Resolution Note (fix version 2023.3.0a19):
Fixed case where Importing sprite sheet by using ISpriteEditorDataProvider generates broken Sprites
Resolution Note (fix version 2023.2.5f1):
Fix for this issue is available on Unity 2023.2.5f1 and above