Search Issue Tracker
Fixed in 2020.2
Fix In Review for 2018.4, 2019.4
Fixed in 2020.1
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] Can't relocate the caret in Input Fields when Hide Mobile Input option is being used
- Multiple Edge Colliders 2D can be edited at the same time, every Edge Collider's "Edit Collider" button is highlighted
- Crash on SceneVisibilityState when trying to open a project containing another project in the Assets folder
- Reflection probe bounces don't work when Rendering Path is set to 'Deferred'
- Shader error undeclared identifier "UNITY_TRANSFER_LIGHTING" when building project
Resolution Note (fix version 2020.2):
Fixed in 2020.2.0a3
Resolution Note (fix version 2020.1):
Fixed in 2020.1.0b2