Search Issue Tracker
Fixed in 2020.1.X
Votes
0
Found in
2017.4.0f1
2018.4.0f1
2019.1.0a1
2019.2.0a1
2019.3.0a1
2019.3.0a11
Issue ID
1173929
Regression
No
[VCS] Provider.Submit disconnects Perforce when trying to submit assets that haven't been checked out
How to reproduce:
1. Extract the attached project to your preferred Perforce workspace and open it
2. Connect it to Perforce
3. Submit the Assets folder
4. Go to "Test" -> "AssetList" to use Provider.Submit on the Scene.unity asset
Expected result: an error is thrown that there are no checked out files in the given asset list and Perforce remains connected
Actual result: a "No files to submit" error is thrown and Perforce disconnects
Reproduced in: 2019.3.0a12, 2019.2.1f1, 2019.1.14f1, 2018.4.6f1, 2017.4.31f1
Note: This occurs when any of the assets in the list are not checked. For example: if there's 1 asset that is checked out and 1 asset that isn't in the asset list, Perforce will still disconnect on Provider.Submit
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 when attempting to create a custom FMOD DSP unit
- [Linux] Floating windows do not keep their size after restarting the Editor
- .framework plugin is mistakenly treated as a directory when building for Universal Windows Platform
- Artifacts appear on GameObjects when using the WebGL Player on Silicon macOS
- Only the icon of the disabled child GameObject is faded when a parent GameObject is a Prefab
Resolution Note (fix version 2020.1):
Fixed in: 2020.1.0a6