Search Issue Tracker
Won't Fix
Votes
0
Found in
2017.3.1f1
Issue ID
1016335
Regression
No
Assert.NotNull passes even though a reference is missing
Steps to reproduce:
1. Open user attached project
2. Open Test Runner window
3. Run All Edit Mode tests, tests should pass
4. Select the file `Assets/beech` in the Project view and delete it
5. Select the file `Assets/Config` and notice that the reference to the sprite is missing.
6. Run the two tests again. `Assert_with_fail` should fail, but `Assert_with_not_null` still passes
Expected result: Assert.NotNull should not pass when reference is missing
Reproduced in: 2018.2.0a5, 2018.1.0b11, 2017.3.2f1, 2017.2.2p1, 2017.1.3p2
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
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- Addressables Profiles and Analyze windows no minimum window size
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Resolution Note:
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 fix for the time being. We understand that this will cause problems for some users, and so may address in a future version.