Search Issue Tracker
By Design
Votes
0
Found in
2017.4.15f1
2018.2.13f1
2018.2.17f1
2018.3.0b11
2019.1.0a9
Issue ID
1094721
Regression
No
[iOS] Unity Build fails: UnityLinker.exe did not run properly!
Steps:
1. Build the attached project ("demo-small.zip")
Expected: successfully build.
Actual: build fails with errors in the Console:
Failed running [...] /Contents/il2cpp/build/UnityLinker.exe [...]
Exception: [...]/Contents/il2cpp/build/UnityLinker.exe did not run properly![...]
Reproduced with: 2017.4.15f1, 2018.2.17f1, 2018.3.0b11, 2019.1.0a9.
Note: not reproducible when building for Standalone and Android.
-
cyclSunity
Sep 16, 2020 23:08
Hey this bug isn't just in versions
2017.4.15f1
2018.2.13f1
2018.2.17f1
2018.3.0b11
2019.1.0a9
It's in 2019.3.15f1 too!
Please help.
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
- [Mobile] Developer Console does not appear when an error is thrown
- [HDRP] Game view renders artifacts when Camera's Component "Post Anti-aliasing" is set to "TAA" and Dynamic Resolution's "Forced Screen Percentage" is changed
- A deactivated Prefab's name color becomes white when a GameObject in the scene is deactivated
- The Game view becomes blank when using Frame Debugger with MSAA and Texture binding enabled in Play Mode
- NullReferenceException is thrown when changing the Inspector preview selection
Resolution Note:
The problem is related to the iPlayDealUnitySDK 2.dll file. This is a managed assembly which was built with the name UnitySDK.dll. It looks like the file was renamed at some point. Unity does not support changing the name of managed assemblies like this after they are built. If I change its file name to UnitySDK.dll, this problem does not occur.