Search Issue Tracker
Fixed in 2020.2.X
Fixed in 2018.4.X, 2019.4.X, 2020.1.X
Votes
0
Found in
2018.4
2018.4.15f1
2019.2
2019.3
2020.1
Issue ID
1217556
Regression
No
[IL2CPP] Type of Arrays with explicitly defined zero lower bound is incorrect in IL2CPP and differ from Mono
Steps to reproduce:
1. Open the attached project (case_1217556.zip)
2. Enter Play Mode
3. Take note of the Object types outputted to the Console (most importantly, the second line - "Explicit zero lower bound array type")
4. Build the project as Standalone, with Scripting Backend set to IL2CPP and Development Build checked
5. Run the executable
6. Compare the Console output to the one in Step 3
Expected result: Arrays with explicitly defined zero lower bound are of the same type in Mono and IL2CPP (both GameObject[])
Actual result: Array with explicitly defined zero lower bound types differ (GameObject[*] in IL2CPP)
Reproduced in: 2018.4.17f1, 2019.2.21f1, 2019.3.1f1, 2020.1.0a22
Cannot test with: 2017.4.36f1 (No IL2CPP)
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
- [Android][URP][OpenGLES3] Render Texture memory increases by 50% when using OpenGLES 3
- MouseButton(0) loses click state when using Device Simulator and enabling "Any iOS Device" in Unity Remote
- [Linux] "Sending message header failed (11)" Warning in Console when opening or closing Standalone Profiler
- [Backport] MacOS Targetsupport Installers for Linux overwrite their content
- [Backport] Scheduled items, asynchronous tasks, and Update() are not run when EditorWindow is opened using ShowModalUtility()
Resolution Note (fix version 2020.2):
Fixed in 2020.2.0a3
Resolution Note (fix version 2020.1):
Fixed in 2020.1.0b2
Resolution Note (fix version 2019.4):
Fixed in 2019.4.5f1
Resolution Note (fix version 2018.4):
Fixed in 2018.4.26f1