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
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
Add comment