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
- [URP] All materials render black when building via batchmode or without rendering Scene/Game view in Editor if Decal renderer Technique is set to "Automatic"
- Player Tags list shows extra blank space behind the scrollbar in the "Player Tags" settings window
- Edit Angular Limits gizmo handles are small and easy to miss-click in the Scene view
- Duplicate Player Tag save fails silently with no error or validation message
- Letters on the left side move further as Letter Spacing is increased when Advanced Text Generator is used and Alignment is set to Center
Add comment