Search Issue Tracker
Fixed
Votes
0
Found in
2019.3.0a3
Issue ID
1155263
Regression
No
[Improved Prefab] "Assertion failed" Exception is thrown on after reverting changes in prefab
"Assertion failed" Exception is thrown on after reverting changes in prefab
Steps to repro:
1. Create a new Project
2. Hierarchy > Create Empty
3. Add Line Renderer component on the empty GameObject
4. Select GameObject > Drag in Project > Asset to make prefab
5. Hierarchy > GameObject > Delete
6. Drag and drop prefab GameObject into the Hierarchy
7. Gameobject > Inspector > Line Renderer > Edit > Light probes > Blend Probes
8. AnchorOverride > select icon > Assign Main Camera
9. AnchorOverride > right-click > Revert
Actual Result: Assertion failed on Expression error is thrown
Expected Result: Changes reverts
Reproducible on :
2019.3.0a3, 2019.3.0b3, 2019.1.0f2, 2018.3.0f2
Environment:
Mac and Windows
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note:
This issue is fixed