Search Issue Tracker
Won't Fix
Won't Fix in 6000.0.X
Votes
0
Found in
2021.3.45f1
2022.3.50f1
6000.0.23f1
Issue ID
UUM-84134
Regression
No
Prefab variant reference is lost when assigned by click-and-drag in Prefab Editor mode
How to reproduce:
1. Open the attached “IN-85814“ project
2. In the Project window (Project → Asset), double-click on the “Test Variant” prefab
3. In the Inspector window, drag the “Test Variant” prefab from the Project window into the ‘Prefab’ field of the “Prefab Reference Test” component
4. In the Hierarchy window press '<' to exit the Prefab Editor
5. Select the “Test Variant” prefab in the Project window
6. Observe the Inspector window
Expected result: The “Test Variant” prefab is assigned to the ‘Prefab' field
Actual result: The 'Prefab' field is set to 'None’
Reproducible with: 2021.3.45f1, 2022.3.50f1, 6000.0.23f1
Reproduced on: macOS (Intel) (user), Windows 11
Not reproduced on: No other environment tested
Notes:
- The bug does not occur if the “Test Variant” is selected by clicking on the 'Prefab’ field directly
- The issue only occurs with prefab variants, not with regular prefabs
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
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
- Addressables content build fails but the Player build is successful when building a development build
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.
Resolution Note (6000.0.X):
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.