Search Issue Tracker
Won't Fix
Votes
0
Found in
5.3.3f1
Issue ID
786856
Regression
No
[OnPostprocessAllAssets] Asset movement isn't detected in certain circumstances
Steps to reproduce:
1. Open attached project
2. In project tab, click "Show in explorer"
3. Rename asset "B" to "C", do the same to its .meta file
4. Rename asset "A" to "B", do the same to its .meta file
5. Get back to the editor
6. In console, notice OnPostprocessAllAssets result:
-------- OnPostprocessAllAssets --------
importedAssets:
Assets/B.prefab
Assets/C.prefab
deletedAssets:
Assets/__DELETED_GUID_Trash/0eb17062d838ea743a94bfd343d45f75
movedAssets:
Assets/A.prefab -> Assets/B.prefab
Expected result: movement between B to C should be detected as well
Reproduced with: 5.1.4f1, 5.2.4f1, 5.3.4p2, 5.4.0b14
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
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
Resolution Note (2019.1.X):
Hi there,
We really appreciate your contribution to the Unity product. Thank you for reporting this issue. We take every case submitted to us seriously by investigating the impact on you, our customer, as well as the impact it may have on the engineering and experience of our product.
This particular case has been investigated thoroughly and we have decided, in the interests of protecting the stability and features of Unity for users that rely upon the affected versions, to not address this fix for the time being. We understand that this will cause problems for some users, and so may address in a future version.
Unity QA Team