Search Issue Tracker
Fixed in 2017.1.X
Votes
0
Found in
5.6.0b11
Issue ID
893519
Regression
No
[IL2CPP] Errors when building the project: Failed running, Exception: [...] did not run properly!
A bunch of long Errors appear when trying to build the project using IL2CPP.
Steps to reproduce:
1. Open User's attached project (uploaded to ownCloud)
2. Switch platform to iOS or Android
3. Open Player Settings and make sure that Scripting Backend is set to IL2CPP
4. Build the project
Result:
Errors appear in the Console:
1. Failed running [...] -l none -c link -b true -x [...]
2. Exception: /Applications/Unity56b11/Unity.app/Contents/Tools/UnusedByteCodeStripper2/UnusedBytecodeStripper2.exe did not run properly!
Reproduced with: 2017.1.0a4, 5.6.0f1, 5.5.2p3
Not reproduced with: 5.4.5f1 (due to Errors in the Console)
Note: reproduced with both iOS and Android.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Android] Error "Blitter is already initialized" is present when Adaptive Probe Volumes are used with OpenGLES3
- VFX Graph effect instance stops rendering when a second instance of the same effect starts 2 frames later
- Operations on the Color32 array are not reflected in WebGL Player when HDR is off
- Rigidbody moves away from the original GameObject when Center of Mass is set in every frame
- WebGL Player does not proceed beyond logo screen when "Target WebAssembly 2023" is enabled
Add comment