* Run "make run-watchos-dev-System.Runtime.Serialization CONFIG=Release" in xamarin-macios/tests
> [FAIL] UniqueIdTest.Ctor_Id : System.NullReferenceException : Object reference not set to an instance of an object.
Complete test log: https://gist.github.com/rolfbjarne/e92d1cf89f7d3985e1cfa481dfb53a59
Complete build log: https://gist.github.com/rolfbjarne/dd0401611192e97e60ca44c7e91aa32c
This does not happen with d15-4 nor d15-3, so it's a regression.
It only happens with watchOS on device in Release mode.
This test code fails:
> new int .Concat (new int ).ToArray ();
while this works:
> new object .Concat (new object ).ToArray ();
it fails somewhere inside .ToArray:
> System.NullReferenceException: Object reference not set to an instance of an object.
> at System.Collections.Generic.ArrayBuilder`1[T].First () <0x39550d + 0x00064> in <160d2620587c4d0eb0956e998349bb70>:0
> at System.Linq.Enumerable+Concat2Iterator`1[TSource].ToArray () <0x38cfa1 + 0x00442> in <160d2620587c4d0eb0956e998349bb70>:0
> at System.Linq.Enumerable.ToArray[TSource] (System.Collections.Generic.IEnumerable`1[T] ) <0xa9d37 + 0x001a0> in <160d2620587c4d0eb0956e998349bb70>:0
Created attachment 25305 [details]
Note that the fix has only been tested on desktop, not on watchos.
I've tested the fix locally on watchOS, and it works.
Created attachment 25378 [details]
XI test project
Attaching XI test project for QA.
* Open project
* Select the monotouch-test-watchos-app project as the startup project
* Select Release|watchDevice as the configuration
It will print "FAILURE!" to the application output when failing, and "SUCCESS!" if successful.
Backport to 2017-06 at https://github.com/mono/mono/pull/5855
Backport to d15-5-2017-06 at https://github.com/mono/mono/pull/5859
Backport to 2017-06 at https://github.com/mono/mono/pull/5855 has been merged with https://github.com/mono/mono/commit/e66d9abbb271c3d08589c09afce4afc80de2d3b6
Backport to d15-5-2017-06 at https://github.com/mono/mono/pull/5859 has been merged with https://github.com/mono/mono/commit/4005b8a4a6b9ee57c60cb02dc901bc96f027d7ca
@Ludovic, is this fix in 2017-10 already? If not we'd need it there too to not regress d15-6.
finally fixed in d15-5: https://github.com/xamarin/xamarin-macios/commit/25c6ba1ebe39bbe95b9dd74efc6d40ba26e262ee
I couldn't find this fix in 2017-10, so I created a PR for it: https://github.com/mono/mono/pull/5887
Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
Mono organizations on GitHub
to continue tracking issues. Bugzilla will remain available for
reference in read-only mode. We will continue to work on open Bugzilla
bugs, copy them to the new locations as needed for follow-up, and add
the new items under Related Links.
Create a new report for Bug 59956 on Developer
Community or GitHub if you have new information to add and do not yet see a matching
In special cases on GitHub you might also want the comments:
GitHub Markdown with public comments
Our sincere thanks to everyone who has contributed on this bug tracker
over the years. Thanks also for your understanding as we make these
adjustments and improvements for the future.