Search Issue Tracker

Fixed in 2020.2

Planned for 2020.1

Votes

1

Found in

2019.3

2020.1

2020.1.0b6

2020.2

Issue ID

1241237

Regression

No

[Code Stripping] Standalone builds fail with 'UnityLinker.exe' errors when making development builds with code stripping enabled

IL2CPP

-

Reproduction steps:
1. Open the user's attached project ("Core.zip")
2. Try making a Standalone Development build with code stripping enabled

Expected result: Build succeeds without errors
Actual result: Build fails with UnityLinker errors

Reproducible with: 2019.3.14f1, 2020.1.0b9, 2020.2.0a11
Couldn't test with 2018.4 (errors after downgrade)

Notes:
1. The issue does not reproduce on empty projects
2. Release IL2CPP builds are built without issues
3. Release Mono builds are built without issues regardless of code stripping settings
4. Development IL2CPP/Mono builds with code stripping enabled reproduces the issue
5. On 2019.3 branch, only IL2CPP builds are affected

  1. Response avatar

    Resolution Note (fix version 2020.2):

    Fixed in 2020.2.0a13

Comments (2)

  1. Ad8cb198ea70ce8cc1ca8f1a564bc90a?d=mm

    tommohawkaction

    May 31, 2020 21:35

    Hi, is there anyway we could get a fix for Unity 2019.3

  2. 801e1953601763cc255b7f8316c75474?d=mm

    eugene_fed

    May 12, 2020 18:09

    So, I have this problem on WebGL and iOS builds. When I create a game for Android, Unity uses Mono, and everything works fine. But for the other two, only IL2CPP mode is required, in which a UnityLinker error occurs. The support manager said in response to my bugreport that everything works fine for him. However, based on the logs, some files on my machine are missing. Unfortunately, I could not find out which files are missing and why they are not installed with Unity.

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.