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
- Crash on SceneVisibilityState when trying to open a project containing another project in the Assets folder
- Reflection probe bounces don't work when Rendering Path is set to 'Deferred'
- Shader error undeclared identifier "UNITY_TRANSFER_LIGHTING" when building project
- Shader effect with specific view disappears when multiple materials in scene are present
- Crash on ShaderLab::IntShader::CreateLocalKeywordRemap when loading custom shaders on standalone build
Add comment