Search Issue Tracker
Won't Fix
Votes
0
Found in
2017.3.0f3
2017.4.0f1
2018.3.0a1
2019.1.0a1
2019.2.0a1
Issue ID
1146092
Regression
No
Script component called "Object" cannot be assigned to a field in the Inspector
How to reproduce:
1. Open the attached "case_1146092-ObjectField" project
2. Select "Tester" in the Hierarchy
3. Drag the "NotObject" from the Hierarchy to the "N Obj" field in the Inspector, the component should successfully be assigned to the field
4. Drag the "Object" from the Hierarchy to the "Obj" field in the Inspector
Expected results: The component is assigned to the field
Actual results: The field is still empty
Reproducible with: 2017.4.26f1, 2018.3.13f1, 2019.1.0f2, 2019.2.0a12
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
- “FMOD failed to set the software format to the custom sample rate…” warnings are thrown as System Sample Rate value is being changed in Audio section of Project Settings window
- VFX Marquee selection does match the visual indicator
- “Invalid AABB aabb” errors are spammed when “Infinity” value is entered in Collider Component fields
- Editor Role does not sync with the MPPM Play Mode Scenario Role when entering Play mode
- Long asset names cause overlap with the “Find” function in search result tabs
Resolution Note (2020.1.X):
We really appreciate your contribution to the Unity product. Thank you for reporting this issue. We take every case submitted to us seriously by investigating the impact on you, our customer, as well as the impact it may have on the engineering and experience of our product.
This particular case has been investigated thoroughly and we have decided, in the interests of protecting the stability and features of Unity for users that rely upon the affected versions, to not address this issue.