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
Developer Community or GitHub 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.
When using the Microsoft.AspNet.WebApi.Client NuGet package and the Unified API the builds are taking longer than usual and I'm seeing the following in the build output:
MTOUCHTASK: warning MT3005: The dependency 'System.Threading.Tasks, Version=126.96.36.199, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' of the assembly 'System.Net.Http.Formatting, Version=188.8.131.52, Culture=neutral, PublicKeyToken=31bf3856ad364e35' was not found. Please review the project's references.
MTOUCHTASK: warning MT3006: Could not compute a complete dependency map for the project. This will result in slower build times because Xamarin.iOS can't properly detect what needs to be rebuilt (and what does not need to be rebuilt). Please review previous warnings for more details.
Is there a way to fix this issue?
It looks like you're using assemblies that are not:
* built against the mobile profile (the SDK that we ship with Xamarin.iOS); or
* built against a PCL profile that is supported by Xamarin.iOS
Such cases might work, it really depends on what's being used by those assemblies, but there are some drawbacks (like the one you're seeing).
If you attach a small test case that result in the above, we can try to see what's exactly going on and suggest options.
We have not received the requested information. If you are still experiencing this issue please provide all the requested information and re-open the bug report. Thanks!