Search Issue Tracker
Duplicate
Votes
0
Found in
2019.3.0a4
2020.1.0a1
2020.1.0a3
Issue ID
1181127
Regression
No
[VCS] Only the asset files are submitted when using Provider.Submit on folders
How to reproduce:
1. Add the attached project ("Provider.Submit Folder.zip") to your preferred workspace and open it
2. Connect it to Perforce and submit the initial project (Assets/Project Settings)
3. In the Project Window check out the "Test" folder (the folder's .meta file and the 3 materials within should get checked out)
4. Go to "Simple Window" -> "Submit" to submit the folder
5. Observe the Version Control window
Expected result: both the checked out asset files and their .meta files in the folder are submitted without issues
Actual result: only the asset files in the folder are submitted and the .meta files remain checked out
Reproduced in: 2020.1.0a3, 2019.3.0b2, 2019.3.0a4
Not reproducible in: 2019.3.0a3, 2019.2.3f1, 2018.4.8f1, 2017.4.32f1 (In these versions the folder contents aren't submitted at all)
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Add comment