Search Issue Tracker
Won't Fix
Votes
1
Found in
2022.3.20f1
2023.2.11f1
2023.3.0b8
Issue ID
UUM-64510
Regression
No
Error in the Console when generating a PropertyBag for a Type that derives from a partial type with a private member
How to reproduce:
1. Open the attached “PropertyBagBug.zip“ project
Expected result: No errors in the Console
Actual result: “error CS0122: 'BaseClass._somePrivateField' is inaccessible due to its protection level“ errors in the Console
Reproducible with: 2022.3.20f1, 2023.2.11f1, 2023.3.0b8
Couldn't test with: 2021.3.35f1 (Different errors in the Console)
Reproducible on: macOS 14.2.1 Sonoma (Intel)
Not reproducible on: No other environment tested
Notes:
- The issue reproduces when a property bag is generated for a type that derives from any partial type with a member that has “[CreateProperty]” or “[SerializeField]” and is not directly accessible from the derived type (private)
- The issue also reproduces if the “_somePrivateField” variable is “protected” or “private protected” in the “BugExample“ Script
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
- Required SpriteMask class (ID 331) is stripped when "Strip Engine Code" is enabled
- “Maximized serialized file backup not found” error is thrown when minimizing a window in a newly opened project
- Build stack trace contains invalid lines when building with IL2CPP using scripts with delegates containing generic types in the signature
- Entities Systems window has a “Show Full Player Loop” dropdown which does nothing when clicked after enabling “Show Full Player Loop”
- Entities Hierarchy Search “Show/Hide” button’s Lens Icon is blurry when the Editor is on an external monitor
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.