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
- [macOS] Editor window is not restored to previous position when launching the Editor and mouse cursor is on a different screen
- [Usability] Warning message in an Adaptive Probe Volume Component is not informative enough when Realtime Global Illumination is enabled
- Inspector for Adaptive Probe Volumes is not repainted when toggling Realtime Global Illumination setting in the Lighting Window
- Surface Inputs are not rendering when using the custom BaseShaderGUI
- Reflection Problem custom Cubemap loses its reference when HDR is enabled and the platform is switched
Add comment