Search Issue Tracker
Fixed in 2020.1.X
Fixed in 2019.2.X, 2019.3.X
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
- Standard Unity Materials and Shaders become corrupted after importing specific Asset Packages
- [Linux][OpenGL][Vulkan] Draw calls are not shown in the Event List when taking a capture of a frame with RenderDoc
- Inaccurate collision detections when Rigidbody Collision Detection is set to "Continuous" or "Continuous Dynamic"
- Crash on Object::IncrementPersistentDirtyIndex when upgrading project version
- [iOS] Multiple Xcode project instances created before opens up when performing Build and Run for iOS Platform
Add comment