Search Issue Tracker
Fixed in 1.1.2
Votes
0
Found in [Package]
1.1.1
Issue ID
1189000
Regression
Yes
Updating the Rider package to version 1.1.1 throws inaccessibility due to protection level errors
How to reproduce:
1. Create a new Unity project
2. Update the Rider package to version 1.1.1
Expected result: no errors are thrown
Actual result: a bunch of errors regarding inaccessibility due to protection levels are thrown
Reproducible with: 2019.2.8f1, 2019.3.0b1
Not reproducible with: 2019.3.0b2, 2019.3.0b6, 2020.1.0a8
Could not test with: 2017.4.33f1, 2018.4.11f1(Rider package unavailable)
Reproducible with package versions: 1.1.1
Not reproducible with package versions: 1.1.0
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Create Node Menu is not closing and “NullReferenceException: Object reference not set to an instance of an object” error is thrown when Shader Graph window is closed
- Assert error is thrown when the Editor language is set to one of the experimental ones in an HDRP project
- A BatchDrawCommand is using a pass from the shader “Universal Render Pipeline/Particles/Lit” that is not SRP Batcher compatible
- The Scene does not get rendered in the Player when MSAA is enabled and more than one Camera is used
- Crash on mono_object_get_class when generating Font Atlas of a specific font file
Add comment