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

  1. 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.

Comments (1)

  1. samuelbrcks

    Oct 29, 2024 02:38

    We all experience some things in life that words can not really explain, even if you say it will be hard to believe but this true i met with a legitimate cyber security company who can help with any cyber problem you just name it and they deliver on point, like i said it will be hard to believe but if you do not try you can never get a result of any such , premiumhackservices AT gmail DOT com at you disposal, my honest advice is to make use of them not just dispose them.

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.