Search Issue Tracker
Won't Fix
Votes
0
Found in
2019.4
2020.3
2021.1
2021.2
2021.2.0b11
2022.1
Issue ID
1364872
Regression
No
The exception appears after changing deleted scenes order at Build Settings > Scenes in Build
Reproduction steps:
1. Create a new project
2. Create 3 scenes ('1', '2', '3') and move them to Build Settings > Scenes in Build
3. In the Project window delete scenes '1' and '3' (make sure that in the Build Settings, these scenes are from the edges)
4. Reopen Unity with this project
5. Move the '1' scene next to the '2'
6. Observe the error in the Console
Expected result: Error doesn't appear
Actual result: Exception appears:
ArgumentException: Could not find item with id: 1016602987. FindItem assumes complete tree is built. Most likely the item is not allocated because it is hidden under a collapsed item. Check if GetAncestors are overriden for the tree view.
Reproducible with: 2019.4.31f1, 2020.3.20f1, 2021.1.25f1, 2021.2.0b16, 2022.1.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
- Opening Terrain Prefab in Prefab Editing Mode throws "NullReferenceException" error
- [Search] Dragging query pills put them behind the search text field
- A CustomPropertyDrawer that returns a PropertyField for a property named the same as a child field will not render all child fields
- Graphics Settings shows default values instead of the real values in the Rendering Debugger when Volume.profile is assigned via script
- Deleting multiple Tags throws “NullReferenceException”, and "Retrieving array element that was out of bounds" errors when holding the Enter key
Resolution Note:
Deleted scenes are left in the scenes list (as opposed to automatically removed) only so the user knows some scenes have disappeared. We support moving them around, or other actions to make sure the project does not break, but it is expected that soon after finding deleted entries, the user cleans them up from the list.
Since the rearranging still works, but logs an error, this is not high enough priority for us to fix right now.