Search Issue Tracker
Third Party Issue
Votes
0
Found in
2020.3.42f1
2021.3.15f1
2022.1.24f1
2022.2.1f1
2023.1.0a22
Issue ID
UUM-20599
Regression
No
Created Import Issue Asset doesn't show up in the Project window until the Unity Editor is restarted
Reproduction steps:
- Open the attached “ReproProject.zip” project
- Select ImportTest > CreateIssueFile in the Toolbar
- Observe the files in the Assets folder using the Project window
Expected result: “test” Import Issue Asset is missing
Actual result: “test” Import Issue Asset is present in the Asset folder
Reproducible with: 2020.3.42f1, 2021.3.15f1, 2022.1.24f1, 2023.1.0a22
Reproducible on: Windows 10 (21H2)
Note: After restarting the Editor “test” Import Issue Asset appears
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:
There are 2 issues here:
1. You need to call something like
AssetDatabase.ImportAsset("Assets/test.importissue"); or AssetDatabase.Refresh() for the new asset to show up, after you've used File.Create or variants.
2. There is currently a known issue (which is not public yet) around creating empty files and ADB which will get looked at :)
But for this specific case you need to do something from #1