Search Issue Tracker
Won't Fix
Votes
0
Found in
2019.4
2019.4.4f1
2020.1
Issue ID
1264760
Regression
No
[IL2CPP] Build fails with multiple errors when building a specific project on Standalone
How to reproduce:
1. Open user's attached "AddressableTest.zip" project
2. Make sure IL2CPP backend is selected (Edit > Player > Scripting Backend)
3. Go to the Build Settings (File > Build Settings...)
4. Build the project on Standalone
Expected result: Project builds successfully
Actual result: Project fails to build with multiple Console errors such as "Failed running D:\Program Files\2019.4\2019.4.8f1_60781d942082\Editor\Data\il2cpp/build/deploy/net471/il2cpp.exe --convert-to-cpp --emit-null-checks"
Reproducible with: 2019.4.8f1, 2020.1.1f1
Not reproducible with: 2020.2.0a19
Could not test with: 2018.4.26f1 (multiple unfixable Console errors)
Notes:
- Could be potentially related to non-ASCII characters underlying somewhere in the project
- "HD Render Pipeline Wizard" pop-up can be ignored as it doesn't affect the outcome of the build
- Error messages could differ when testing locally, however, the issue reproduces on the same versions
- Builds without any issues when using Mono backend instead of IL2CPP
- Earliest version this builds successfully in is 2020.2.0a18
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
- Certain textures are incorrectly marked in the render pass list when observed through Render Graph Viewer
- "Assertion failed on expression" error occurs when multiple Animation Components are instantiated after changing the Culling Type
- MacOS persistentDataPath uses old path when built compared to Editor Play mode
- Crash on RaiseException when entering Play Mode in a specific project
- Debug Console does not reappear when disabling and re-enabling Debug.developerConsoleEnabled
Resolution Note:
This issue is corrected in 2020.2 and later. We do not plan to back port the fix to earlier versions of Unity.