Search Issue Tracker
Won't Fix
Votes
0
Found in
2020.3.42f1
2021.3.13f1
2022.1.21f1
2022.2.0b15
2023.1.0a19
Issue ID
UUM-19086
Regression
Yes
Type mismatched reference value is not null when checked in Player
Reproduction steps:
1. Open the “ticket-1385501-type_mismatch“ project
2. Build And Run
3. Open Player.log and search “object is not null“
Expected result: the Player does not crash and the search returns 0 results
Actual result: the Player crashes and the search returns 1 result
Reproduced in: 2020.3.20f1, 2020.3.42f1, 2021.3.13f1, 2022.1.21f1, 2022.2.0b15, 2023.1.0a19
Not reproduced in: 2020.3.19f1
Reproduced using: Windows 11, macOS Monterey 12.0.1 (Intel)
Note: not reproduced in Editor / Play Mode
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 "Search session timeout for provider "asset"" is logged in Console when Search by Type is selected for some time
- Directional shadows render only according to first Directional Light when the second Directional Light is the brightest light
- Entities are jittering when Temporal Anti-aliasing (TAA) is applied
- The drawing order of Transparent objects is incorrect when changing the Material from Opaque to Transparent with GPU Resident Drawer enabled
- Sprite animations do not update when Animator parameters change in the Player
Resolution Note:
The repro case seem to contain a scene with an object whose meta file was removed, and thus the scene is corrupted. On the editor side we have a slightly different way of handling with "missing" type information to try to enable the user fix things. That explain the difference of behavior seen here.
Unfortunately we can't do anything to fix the crash: the scene needs to be manually fixed by the user.