Search Issue Tracker

By Design



Found in







Issue ID




[VCS] No assets are submitted using Provider.Submit when there's at least one local asset in the given asset list

Version Control


How to reproduce:
1. Add the attached project ("") to your preferred workspace
2. Open it and connect it to Perforce
3. Submit the "1" material and keep the "2" material unsubmitted as a local asset
4. Check out the "1" material and go to "Simple Window" -> "Submit" to submit both "1" and "2" materials
5. Observe the console and the material status

Expected result: the "1" material is submitted and the "2" material is not (Or alternatively another prompt is called letting the user choose whether to submit just the submittable assets or nothing at all)
Actual result: neither material gets submitted and a "Version Control: Files must be added before they can be submitted" error is thrown

Reproduced in: 2020.1.0a3, 2019.3.0b2, 2019.2.3f1, 2018.4.8f1, 2017.4.32f1

Note: only reproduces when submitting with Provider.Submit, the context menu correctly filters out the local assets

  1. Resolution Note:

    This is by design, the Provider API does not do any filtering for the given asset lists. If there are any unsubmittable assets in the asset list it is expected that the submit task will fail.

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.