Search Issue Tracker
Postponed means that the issue was either a feature request or something that requires major refactoring on our side. Since that makes the issue not actionable in the close future we choose to close it as Postponed and add it on our internal roadmaps and technical debt pages instead.
Postponed
Votes
0
Found in
4.3.4f1
Issue ID
596820
Regression
No
Stripping fails when two methods' generic parameters differ in DLL
Postponing reason:
This is an issue with the stripper incorrectly stripping overloaded generic methods. We are not going to fix this bug for a mono backend, as fixing it would require major changes to core libraries, which could introduce regressions during this sensitive timing (5.0 release, iOS 64 bit upgrade, etc). On the other hand il2cpp backend will use a new stripper, where this bug is already fixed. That being said AOT error reporting has been improved, so in issues like these Unity will capture AOT errors correctly, and will include what methods are missing, so they can be specified in link.xml file to avoid their stripping.
Description:
Stripping fails when you have two methods in a DLL which have the same name, but differ in their generic parameters.
To reproduce:
1. Create a new project
2. Import the attached .unitypackage
3. Set the stripping to "ByteCode" or "Assemblies"
4. Note the "Failed AOT cross compiler" error in the console
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- PlayerPropertiesChanged event fires before Player Properties are applied
- Opening Media Pop-out in “Before You Start” Tutorial throws “Styles” and “Styles_Dark” messages in the Console window
- Play Mode Scenario selection/highlight is too long and out of its bounds when the Play Mode Scenario window is opened after maximizing
- Asset name is not shown in the Undo History window when a sprite is modified
- Moving a Tab to a floating window fails when floating windows are docked next to each other
Add comment