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
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.
Please create a new report on
GitHub or Developer Community with
your current version information, steps to reproduce, and relevant error
messages or log files if you are hitting an issue that looks similar to
this resolved bug and you do not yet see a matching new report.
We are going to land this in 15.2.2:
but it is a total hack.
We need a real solution to:
coming from somewhere lower on the stack.
Marek / Ankit - I guess/believe this was fixed differently in 15.3, can someone confirm / provide details?
Fixed in 15.4:
PR for enabling this for XM:
PR merged in xamarin-macios/master
Backport for d15-4 -> https://github.com/xamarin/xamarin-macios/pull/2562
## Steps to reproduce:
Installed XM 184.108.40.206pkg and mono220.127.116.11 to reproduce the issue mentioned in bug 55988. Installed master build 18.104.22.168.pkg to verify fix.
## Observed Behaviour:
With fix from master build, System.ValueTuple loading is fixed. However, issue reported in https://bugzilla.xamarin.com/show_bug.cgi?id=56574 is reproducible.
Created attachment 24658 [details]
Build Log: https://gist.github.com/GouriKumari/bc0645861b1069dd0cb196b2d307a1c9
Exception Log: https://gist.github.com/GouriKumari/208a7cd6082fb09d2f9f6c2f780d5de2
An update to this bug: Issue mentioned in bug 56574 is still reproducible with d15-3 stable and d15-4 alpha builds. It seems the hack included in 15.2.2 service release wasn't included in d15-3.
## Supplemental Info:
Issue is fixed only in 15.2.2 service release
Build Log: https://gist.github.com/GouriKumari/75c7daed017a7b45796c3e27000a8077
Application Output: https://gist.github.com/GouriKumari/f3355f5b1fcc7b4983ebe490a3460858
The earlier hack was removed. And a new hack/fix was added in https://github.com/mono/msbuild/commit/c907a5182a101624eb58e73fb24f97666abf477a .
Can you attach the diag build log with 15.4 and the test project that you used?
I tested with XM master build 22.214.171.124 and I could reproduce the issue.
## Build Log:
Retested with XM master build 126.96.36.199. TestRosylnApp builds and launch successfully with Xamarin.Full config.
Build Log: https://gist.githubusercontent.com/GouriKumari/685d4d8fb5a56818e92daa1785e16317/raw/04de255f266d541c61e2afd7474eace6f36f1208/gistfile1.txt
## Test Env: