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
- Red spots appear when Blending Lighting Scenarios using Adaptive Probe Volumes
- [Windows] About Unity Window needs to be opened twice to adapt to resolution
- NullReferenceException and temporary graph corruption after entering playmode if output node connection was changed
- Sprite Renderer with Animation does not reflect Sprite changes in the Scene when switching Mask Interaction
- User is redirected to a non-existing online documentation link when clicking on "?" help button inside Inspector window while Animator Override Controller is selected
Add comment