Search Issue Tracker
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.0a3
Issue ID
1181112
Regression
No
[VCS] No assets are submitted when there's at least one locked remote 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" and "2" materials
4. Open P4V with a different user and lock the "1" material
5. Check out the "2" material and go to "Simple Window" -> "Submit" to submit both "1" and "2" materials
6. Observe the console and the material status
Expected result: the "2" material is submitted and the "1" 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: File(s) couldn't be locked." error is thrown
Reproduced in: 2020.1.0a3, 2019.3.0b2, 2019.2.3f1, 2018.4.8f1, 2017.4.32f1
Note: Reproduces when submitting multiple assets with the context menu or when using Provider.Submit
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Specular lighting visible in a camera with Path Tracing when Preserve specular lighting is disabled in observed material
- Cinemachine package throws CS1061 errors in the Console when installed in a project that has HDRP and URP installed
- Editor.log file size grows rapidly when a scene exceeds the "Maximum Shadow on Screen" limit setting in the HDRP Asset
- Player build freezes after calling Application.Quit() when the scripting backend is set to IL2CPP
- Texture is not applied on a Custom Render Texture when a Cubemap is selected as the texture
Add comment