We're saying that your code runs as expected for us against the latest framework code in all recent branches, without any crashes or warnings, as far as we can see.
We don't see any fixes having been made specifically for this issue you mention, but several sort bugs have been fixed in the last two weeks, including two yesterday, so a retest seems like the best way forward.
We're not sure why you'd want to know whether there was a temporary regression in a particular build from several weeks ago - you did say that it has since been fixed, right?
Anyway, we've also just added a null check to the code you showed in your stack-trace, just in case. That won't be available until June 12 builds.
Let us know how you get on.
We don't see any fixes having been made specifically for this issue you mention, but several sort bugs have been fixed in the last two weeks, including two yesterday, so a retest seems like the best way forward.
We're not sure why you'd want to know whether there was a temporary regression in a particular build from several weeks ago - you did say that it has since been fixed, right?
Anyway, we've also just added a null check to the code you showed in your stack-trace, just in case. That won't be available until June 12 builds.
Let us know how you get on.
Comment