Search Issue Tracker
Won't Fix
Votes
0
Found in
2020.3.42f1
2021.3.15f1
2022.1.24f1
2022.2.1f1
2023.1.0a22
2023.2.0a1
2023.3.0a3
Issue ID
UUM-20602
Regression
No
Reimporting a Scripted Importer Asset when Profiler is recording will make it null
Reproduction steps:
- Open the attached “ReproProject.zip” project
- Select the “LogAssetStatus” GameObject in the Hierarchy window
- Ensure that the “Test” Import Issue Asset is attached to the “Asset Status” Script Component’s Asset field in the Inspector window
- Open the Profiler (Window > Analysis > Profiler)
- Change Profiler to “Edit Mode” and press the Record button
- Observe the Console window
- Right-Click "test" Import Issue Asset in the Project Browser window and select “Reimport”
- Observe the Console window
Actual result: Multiple "asset.IsValid = False" outputs in the Console window after reimporting the asset
Expected result: Only "asset.IsValid = True" outputs are present in the Console window
Reproducible with: 2020.3.42f1, 2021.3.15f1, 2022.1.24f1, 2022.2.1f1, 2023.1.0a22
Reproducible on: Windows 10 (21H2)
Note: To make the Console output "asset.IsValid = True" again, you need to open any Script, modify and save it
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
- Unity CIL Linker fails on Player build when persistent listeners have "<" and ">" in their XML attribute names
- ”Lighting data asset ‘LightingData’ is incompatible with the current Unity version…” warnings are thrown when saving Indoors (URP) and Outdoors (URP) Scenes as Scene Templates
- [iOS] The screen blinks when transitioning from custom to Unity splash screen
- [macOS] ”Ignoring depth surface load action as it is memoryless” warnings are thrown when taking Game View Snapshot
- UI Builder Inspector scrolls back up when changes on an expanded but not fully displayed Inspector tab are saved
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.