Search Issue Tracker
Fixed in 2019.1.X
Fixed in 2018.2.X, 2018.3.X
Votes
0
Found in
2017.3.0a1
2017.4.15f1
2018.2.12f1
2018.2.16f1
2018.3.0b9
2019.1.0a8
Issue ID
1099608
Regression
No
[IL2CPP] IndexOutOfRangeException is thrown when getting last array value with Array.GetValue()
Steps to reproduce:
1. Download attached project
2. Build "Main" scene for Standalone
3. Open build project
Expected results: No exceptions are thrown
Actual results: Index out of range exception is thrown
IndexOutOfRangeException: Index has to be between upper and lower bound of the array.
at System.Array.GetValue (System.Int32 index) [0x00000] in <00000000000000000000000000000000>:0
at ArrayTest.TestOneDimensionArray (System.Text.StringBuilder textBuilder) [0x00000] in <00000000000000000000000000000000>:0
at ArrayTest.Start () [0x00000] in <00000000000000000000000000000000>:0
Reproduced with: 2019.1.0a8, 2018.3.0b9, 2018.2.16f1, 2017.4.15f1
Tested and reproduced with UWP and Standalone platforms
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
- ArgumentExceptions are thrown when an exclamation mark is written as the first character in the search window
- "No HDR monitor detected." warning is shown in the Rendering Debugger even when the Editor is on HDR-enabled monitor
- Shader Graph Enum Keyword Default Value changes after reordering Entries
- Light Explorer throws “ArgumentException” error when disabling all columns from the Multi-column panel context menu
- "Freeze Camera For Culling" options are inconsistent between the Game view overlay and Rendering Debugger window
Resolution Note (fix version 2019.1):
IL2CPP was not correctly creating 1-index based arrays. This change corrects that problem.