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 the Xamarin.Android .targets file are updated (via an updated packaged for instance), all cache-generating tasks (like _BuildSdkCache) should be re-run.
This would prevent issue where things became out of sync because of an update in XA itself. As an example, when the target framework version was changed from 6.0.99 to 7.0 the old cache wasn't valid anymore albeit still used.
In a general way, you could assume any of the cache-generating task could have had their logic changed after an XA upgrade and so to be safe cache-generating task should be marked up for execution so that the new code runs.
We can probably just add $(MSBuildThisFileFullPath) to the Inputs for the cache generating tasks
Fixed in xamarin-android/master/64fb4b71