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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
Add comment