Search Issue Tracker
Won't Fix
Votes
0
Found in
2020.3.35f1
2021.2.19f1
2022.1.3f1
2022.2.0a13
2023.2.0a1
Issue ID
UUM-3140
Regression
Yes
Manual refresh calls PostprocessTexture before script compilation
How to reproduce:
1. Open the "Refresh_Bug.zip" project
2. Make sure "Auto Refresh" is off in the Preferences
3. Delete .meta files from Assets folder
4. In Project tab press RMB > Refresh
Actual result: AssetPostprocessingInternal.PostprocessTexture is called before script compilation.
Expected result: AssetPostprocessingInternal.PostprocessTexture is called after script compilation.
Reproducible with: 2020.1.0a3, 2019.3.0b2, 2019.2.4f1, 2019.2.0a5.
Not reproducible with: 2019.2.0a4, 2019.2.0a1, 2018.4.8f1, 2017.4.32f1.
Notes:
- The same behaviour happens when refresh is called from Rider, when Auto-Refresh is on and Unity is not focused. (Not reproducible with VS)
- Reproducible with macOS Mojave 10.14.4 and Windows 10.
- Not reproducible with macOS Catalina 15.0.
- This behaviour causes a revert of pulled .meta files from repository.
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
- Crash on when D3D12RenderPass::SetupDeviceResources when opening FBX animation preview
- Serialization errors are thrown when "com.unity.render-pipelines.core" is added as a custom package and Graphics window is opened
- Character Joints unexpectedly rotate when a ragdoll is created using the Ragdoll Wizard
- Crash on GfxDeviceD3D11Base::DrawBuffersBatchMode when rendering the Scene view
- The shared EditorBuildSettings.asset file of symlinked projects is not updated when changing the order of the Scenes in Build Settings in one of the projects
Resolution Note:
Thank you for your bug report.
After reviewing the issue and the impact it has on our users our team has decided that this case will be resolved as "Won't Fix".This does not mean that the issue isn’t a legitimate bug, but instead that we are not able to prioritize the fix, at this time.
The case will now be closed, and will not be reopened unless new information arises that would change the issue’s impact. Please let us know if you have additional information relating to the severity of this bug.