Search Issue Tracker

Fixed in 2019.1.X

Duplicate in 2018.3.X



Found in



Issue ID




Certain LINQ combinations yield wrong results on .NET 4.6



Reproduction steps:
1. Download user's project and open in Unity
2. Enter Play mode

Expected: in the console appears "a, b, c, d, e, f, g, h, i, j"
Actual: in the console appears "a, b, c, d, e, f, g, h, i, NULL"

Reproduced on: 2017.2.0b2; 2017.2.2p2; 2017.3.2f1; 2017.4.0f1; 2018.1.0b12; 2018.2.0a5
Not reproduced on: 2017.1.3p2; 2017.2.0b1
Regression introduced: 2017.2.0b2

Note: with .Net 3.5 works as expected
2017.2.2p2; 2017.3.2f1; 2017.4.0f1 actual result - "a, b, c, d, e, f, j, NULL, NULL, NULL"

Upstream issue

  1. Resolution Note (fix version 2019.1):

    This issue has been fixed. Fix will be available in a future 2018.3 beta (likely b9) and a future 2018.2 version (likely 18.2.15).

Comments (2)

  1. Azim-Palmer

    Oct 20, 2018 12:49

    This is tragic. Makes me worry what other standard parts of the framework I can't use and they won't bother fixing.


    Sep 17, 2018 11:55

    This is a disaster of an issue! How the hell is this postponed when 2013.3 marks .NET 3.5 as deprecated? This absolutely MUST be fixed before .NET 3.5 is removed.

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.