Search Issue Tracker
Fixed in 2022.1.X
Fixed in 2020.3.X, 2021.2.X
Votes
0
Found in
2020.3
2020.3.4f1
2021.1
Issue ID
1351726
Regression
No
It is not possible to add custom linker steps due to a problem with the options parser
How to reproduce:
1. Open the "UnityLinkerTests_.7z" with Visual Studio
2. Go to Test -> Run All Tests
Expected result: Tests are successful
Actual result: Tests fail
Reproducible with: 2020.3.17f1, 2021.1.17f1
Could not test with: 2019.4.29f1, 2021.2.0b7, 2022.1.0a6 (Due to errors when changing netcoreapp3.1 to the version supported on those versions)
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
- “ValidateSchema Error2” error is thrown in the Player when using IL2CPP Scripting Backend
- Symbolic links disappear when a .xcframework file is added through the Unity Editor
- Errors regarding importing occur upon opening a project when the "Library" folder is deleted
- MeshRenderer.sortingLayerID cannot be changed when change is being done in a built Player
- Warnings related to App Icon are being thrown when building project to VisionOS Platform
Resolution Note (fix version 2020.3):
Fixed in: 2020.3.28f1