Search Issue Tracker
Fixed in 1.5.5
Votes
0
Found in [Package]
2019.4
2020.1.11f1
2021.1
Issue ID
1289360
Regression
No
[PlasticSCM]Object reference not set to an instance of an object error when trying to login in
How to reproduce:
1. Open the user's attached project
2. Click on the "User name" field in the "Connect to server" box
Expected result: You can start writing your username
Actual result: Error - Plastic SCM NullReferenceException: Object reference not set to an instance of an object
Reproducible with: 2019.4.14f1, 2020.1.13f1, 2020.2.0b11, 2021.1.0a5
Could not test with: 2018.4.29f1 (no "Connect to server" box)
Comments (1)
-
PictonicStudio
Sep 10, 2021 23:47
Still happening
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Objects with Universal Render Pipeline/Particles/Lit shader are always lit up when changing their Rendering Layer Mask
- PolySpatial “Trying to set shader on a Material Variant.” error is printed in the console when entering Play Mode
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
- Addressables content build fails but the Player build is successful when building a development build
Resolution Note (fix version 1.5.5):
This issue is resolved with the latest version of the Plastic SCM for Unity asset on the Asset Store.