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
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
- White lighting artifact when a point light with a small emission range and "Hard Shadows" touches an object while a directional light with "Soft Shadows" and another point light are present
Resolution Note (fix version 2020.2):
Fixed in: 2020.2.0a4