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 for Bug 59567 on
Developer Community or GitHub if you have new
information to add and do not yet see a matching new report.
If the latest results still closely match this report, you can use the
In special cases on GitHub you might also want the comments:
GitHub Markdown with public comments
With an Android project referencing support libraries (before 188.8.131.52) or Google Play Services, the UpdateAndroidResources target will fail in an IDE context because less things are now being run (in that case, no ResolveAssemblyReferences) triggering an error with the Xamarin.Build.Download targets that are implicitely referenced by those packages.
Repro: run `msbuild /t:UpdateAndroidResources /p:DesignTimeBuild=true /p:BuildingInsideVisualStudio=true /v:diag AndroidApp.csproj`
Outcome: Xamarin.Build.Download.targets(114,3): error : Did not find reference matching RestoreAssemblyResources AssemblyName metadata 'Xamarin.GooglePlayServices.Basement'
Diagnostic log: https://gist.github.com/garuma/294bb5c0f118ff935c40f5e636ec7a2d
This has also the effect that the Android designer will constantly show a warning to users that their resources are likely wrong but where a normal build doesn't exhibit the problem.
We have a pull request open which makes Xamarin.Build.Download explicitly depend on `ResolveAssemblyReferences` target so that no matter how our task is invoked, it should ensure the references are resolved first.
To update comment #1, Dean referred me to a property the designer can set to revert the target to the older behavior which also means this issue won't show up for the designer.
Can we mark this as fixed?