Search Issue Tracker
Third Party Issue
Votes
0
Found in
6000.0.25f1
6000.1.0a2
Issue ID
UUM-85762
Regression
Yes
Building "ManagedStripping" fails when a script uses a custom package
Reproduction steps:
1. Open the attched “BugRepro” project
2. In Project Settings (Edit > Project Settings…) Player tab, set the Scripting Backend to “IL2CPP”
3. Build the Project
Expected result: The build is successful
Actual result: The build fails and “Building Library\Bee\artifacts\WinPlayerBuildProgram\ManagedStripped failed with output:” is logged in the Console
Reproducible with: 2023.3.0b1, 6000.0.25f1, 6000.1.0a2
Not reproducible with: 2021.3.45f1, 2022.3.51f1, 2023.3.0a19
Reproducible on: Windows 11
Not reproducible on: No other environments tested
Note: If you delete the “Assets/Scripts/ErrorScript” script, the build will be successful
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
- Crash on JobQueue::HasJobGroupIDCompleted when closing the Editor while in Play mode on a specific project
- In "Preferences" section the “SpriteShape” menu item, the details page title “SpriteShape”, and “ControlPoint” entries are displayed as code strings rather than formatted UI strings
- Errors thrown constantly when Virtual Offset Debug is enabled and lighting was baked on AMD machine
- Persistent Memory Leak when reloading domain and using Distance-based Ghost Importance
- HDRP project doesn't render in standalone player when using High stripping
Resolution Note:
This is due missing reference in a third party package. An update to that package is available that will resolve this issue: https://forum.arongranberg.com/t/a-5-2-0-failed-to-resolve-assembly-clipper2lib/16904
Please update the package and see if that resolves the error.