Search Issue Tracker
Fixed in 2021.2.X
Fixed in 2019.4.X, 2020.3.X, 2021.1.X
Votes
0
Found in
2019.4.21f1
2019.4.24f1
2020.3
2021.1.0b5
2021.2.0a3
Issue ID
1328322
Regression
Yes
[Android][IL2CPP] "il2cpp.exe did not run properly!" exception appears when building a project that contains a "Live2DUnity.dll"
How to reproduce it:
1. Open the user's attached project "Live2DViewerEX Android Overlay Test.zip"
2. Go to the Project Settings -> Player and set Scripting Backend value to "IL2CPP"
3. Build the project
4. Observe the Console window
Expected results: Building for Android with IL2CPP succeeds
Actual results: Building for Android with IL2CPP fails. "Exception: ...\Editor\Data\il2cpp/build/deploy/net471/il2cpp.exe did not run properly!" appears in the Console window
Reproducible with: 2019.4.21f1, 2019.4.25f1, 2020.3.7f1, 2021.1.0b5, 2021.1.5f1, 2021.2.0a3, 2021.2.0a15
Not reproducible with: 2019.4.20f1, 2021.1.0b4, 2021.2.0a2
Could not test wit: 2018.4.34f1 - due to errors
Notes:
- Not reproducible with Mono Scripting Backend
- Not reproducible with Windows Standalone
- Can be related to 1288271 issue fixes
- Android project can be built after opening an Assets > Live2D > framework > L2DBaseModel.cs file and commenting the 21st line
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
- TreeView Child display toggle styling becomes reversed when clicking and dragging it
- Null is returned when using FocusOutEvent.relatedTarget
- Unity_BaseInstanceID is always zero when rendering multiple meshes and instancing with the same buffer
- UI Document button's text does not resize relatively when size in percentage (%) is used
- Event.current.mousePosition has an offset of 1px along the y-axis in WebGL build when the mouse button is released
Resolution Note (fix version 2021.2):
Fixed in 2021.2.0a21
Resolution Note (fix version 2021.1):
Fixed in 2021.1.10f1
Resolution Note (fix version 2020.3):
Fixed in 2020.3.12f1
Resolution Note (fix version 2019.4):
Fixed in 2019.4.29f1