Search Issue Tracker
Fixed in 2022.2.3f1
Fixed in 2023.1.X
Votes
0
Found in
2022.2.0b6
2023.1.0a8
Issue ID
UUM-12860
Regression
Yes
Prefab isn't marked dirty when replacing a missing Sprite reference in the Prefab View
How to reproduce:
1. Open the attached “IN-12231” project
2. Open the “Prefab Image” from Project Browser in a Prefab View
3. Set the “SecondImage” to the missing “Source Image” field in the Inspector
4. Save and re-open the Prefab
Expect result: “Source Image” field is “SecondImage”
Actual result: “Source Image” field is “Missing (Sprite)”
Reproducible with: 2022.2.0a13, 2022.2.0b6, 2023.1.0a8
Not reproducible with: 2020.3.38f1, 2021.3.8f1, 2022.1.14f1, 2022.2.0a12
Reproduced on: macOS 12.3 (Intel)
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
- [Tile Palette] Sprites not rendering when brush tool "Paint a filled box with active brush" is used for the first time
- Adding available Nodes with longer names in Fragment Context window overflow Fragment Context window in Shader Graph
- "Layer Palette Profile" Asset is automatically applied to the second Terrain but doesn't load any layers
- "Terrain Tools" shortcut conflicts with the Overlays shortcut by default
- Longer Shader Graph Property Reference names breaks VFX Graph Output Particle Node
Resolution Note (fix version 2022.2.3f1):
Fixed by another internal issue: UUM-11402: Replacing missing prefab reference doesn't mark scene as dirty
Resolution Note (fix version 2023.1):
Fixed by another internal issue: UUM-11402: Replacing missing prefab reference doesn't mark scene as dirty