Search Issue Tracker
Fixed in 2022.1.X
Fixed in 2021.2.X
Votes
0
Found in
2021.2
2021.2.0b9
2022.1
Issue ID
1361812
Regression
No
Missing IL2CPP methods errors are thrown on every new build when using IL2CPP stripping engine with low stripping enabled
Different console errors regarding missing/invalid IL2CPP methods and types are thrown on every new build when using IL2CPP stripping engine with low stripping enabled
Reproduction steps:
1. Open the user's attached project
2. Build the project to Android device
Expected result: None or the same console errors are thrown on every new build using IL2CPP stripping engine with low stripping enabled
Actual result: Different console errors are thrown on every new build using IL2CPP stripping engine with low stripping enabled
Reproducible with: 2021.2.0b9, 2022.1.0a10
Couldn't test with: 2019.4.30f1, 2020.3.19f1, 2021.1.22f1 (multiple different Editor errors / missing references are thrown due to downgrading the project)
Note:
Using IL2CPP stripping engine with medium stripping builds project successfully with no errors but the build crashes on Android devices upon start
Comments (1)
-
Mikilo
Nov 29, 2021 18:24
Hi,
Does this fix will be implemented in 2020 LTS?
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
- UI Toolkit meshes are fully rendered and rasterized when opacity is 0
- Light rendering artefacts appear in the Editor when assigning unsupported 3D Custom Render Texture in Camera’s Output Texture, unclearable errors and warnings spammed
- Memory leak when running a test with "GfxThreadingMode" set to "SplitJobs"
- Loading Unloaded unsaved Scene throws “ArgumentException” error in the Console
- Crash on std::__1::__tree_const_iterator when opening the Build Profiles window in a specific project
Resolution Note (fix version 2022.1):
Fixed in: 2022.1.0a15
Resolution Note (fix version 2021.2):
Fixed in: 2021.2.3f1