Search Issue Tracker
By Design
Votes
0
Found in
2017.4.0f1
2018.4.0f1
2019.2.0a1
2019.3.0a1
2020.1.0a1
2020.1.0a3
Issue ID
1181094
Regression
No
[VCS] No assets are submitted using Provider.Submit when there's at least one local asset in the given asset list
How to reproduce:
1. Add the attached project ("Reports.zip") 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
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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
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.