Search Issue Tracker
Fixed in 2019.3.X
Votes
0
Found in
2018.2.0f2
Issue ID
1077431
Regression
No
[Perforce] Passing directory path to Provider.Submit doesn't submit assets inside that directory
Steps to reproduce:
1. Open attached project in perforce workspace
2. Connect to perforce and submit project to repository
3. In top menu, click Test > AssetList
4. In project tab notice that Scenes/SampleScene is checked out but doesn't get submitted
Expected behaviour: AssetList used in repro checked scene out so same AssetList should submit scene too
Code which can be used to reproduce the issue:
AssetList list = new AssetList();
list.Add(new Asset("Assets/Scenes"));
Task t = Provider.Checkout(list, CheckoutMode.Asset);
t.Wait();
Provider.Submit(new ChangeSet(), list, "asd", false);
Reproduced with: 2017.4.10f1, 2018.2.0f2, 2018.2.7f1, 2018.3.0a11
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- The Scene View becomes gray and "NullReferenceException" errors are thrown when attaching the Unity Editor process to RenderDoc
- Memory usage rapidly rises when changing colors in the color wheel
- Physically Based Sky's Horizon and Zenith Tint Color Selection Bars don't have immediate access to color pickers
- EmptyAdditionalLightShadowmapTexture leaks from memory when URP quality level is changed using QualitySettings.SetQualityLevel
- Referenced ScriptableObject field does not get updated and cannot be set to "None" when there are no Objects of that type
Add comment