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
- ACES Tonemapping causes banding artifacts and negative values in ColorGradingLUT when HDR is enabled and "High Dynamic Range" Grading mode is selected while Android Platform is used
- Android Player freezes when an Audio Source is playing and an incoming call is picked up and then hung up and the Audio Source is started again
- Green success icon is poorly visible in the light Unity theme
- Incorrect input into the Input Field when using Microsoft IME Japanese
- Multiplayer role "ClientAndServer" is displayed without the spaces in the "Play Mode Scenarios" window
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