Search Issue Tracker
Fixed in 2020.2.X
Fixed in 2020.1.X
Votes
0
Found in
2017.4.0f1
2018.4.0f1
2019.2.0a1
2019.3.0a1
2020.1.0a1
2020.1.0a7
Issue ID
1188160
Regression
No
[Asset Importing] Pulling folder .meta file deletion does not properly delete the folder with Git
How to reproduce:
1. Have two users on the same Git project with at least one empty folder
2. With user 1: delete the folder and commit/push the deletion
3. With user 2: pull the new changes (empty folder's deletion)
4. Observe that the folder didn't get deleted and that a new folder's .meta file has been created for committing
Expected result: The empty folder is deleted alongside its .meta file on pull
Actual result: The empty folder is not deleted, only its .meta file is resulting in a new one being re-created
Reproduced in: 2020.1.0a7, 2019.3.0b5, 2019.2.7f2, 2018.4.10f1, 2017.4.32f1
Note: Only reproduces with Git, Perforce correctly deletes the folder and its .meta file
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
- Bunch of "TargetParameterCountException" errors thrown in the Editor Console when opening the "Adaptive Probe Volumes" tab in the "Lighting" window
- Non-removable serialized data for a renderer feature still appears even when the renderer feature is deleted
- URP Cascaded Shadows do not have a falloff in Player when the Player is built not in Development Mode
- Grid in animation preview window is rendered on top of the object
- WebGPU Graphics.RenderPrimitives fails on MeshTopology.Quads with Validation errors when exceeding 64k vertices
Resolution Note (fix version 2020.2):
Fixed in: 2020.2.0a4