Search Issue Tracker
Fixed in 2020.1
Fixed in 2019.2, 2019.3
Votes
4
Found in
2019.1
2019.3.0a3
Issue ID
1172818
Regression
Yes
VCS: addition of "ChangeSet changeset = null" argument to Provider.Checkout broke prebuilt assemblies in 2019.1+
Provider.Checkout public API got a new optional argument for the changeset it should get checked out at. This however breaks precompiled assemblies, e.g. https://github.com/googlesamples/unity-jar-resolver/issues/262#issuecomment-515519308 ran into this.
The public API should get changed back to have:
- public static Task Checkout(string asset, CheckoutMode mode) // calls 2nd one with null
- public static Task Checkout(string asset, CheckoutMode mode, ChangeSet changeset)
Instead of one API entry point with a default argument.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Visual C# Compiler cannot find source files because it is looking at old file locations
- Ghost empty folders are left behind when after calling Refresh, Directory.Move is called
- [OSX] The Scene icon in the Unity Editor's title bar can be dragged and dropped out of the project
- [Metal][Editor] Memory grows continuously until Editor crashes when importing 100k materials
- Investigate why .meta files are sometimes not parsed right
Add comment