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.
In Xamarin.Android.Support.Vector.Drawable.targets the argument --no-version-vectors is added like this:
</Project>[Martin-Macbook-Work:packages/Xamarin.Android.Support.Vector.Drawable.23.3.0/build] martin% cat Xamarin.Android.Support.Vector.Drawable.targets~
<?xml version="1.0" encoding="utf-8"?>
<!-- Adds an argument to the call to aapt to support vectors -->
* Xamarin Android Support Vector Drawable MSBuild Tasks
For some reason the string was added three times recursively during the build and ended up like
I could fix the build by manually changing <AndroidResgenExtraArgs>$(AndroidResgenExtraArgs)--no-version-vectors</AndroidResgenExtraArgs> to <AndroidResgenExtraArgs>--no-version-vectors</AndroidResgenExtraArgs>
I don't know why `Xamarin.Android.Support.Vector.Drawable.targets` would apparently be imported three times -- that bears further investigation -- but regardless, `Xamarin.Android.Support.Vector.Drawable.targets` should insert a space:
> <AndroidResgenExtraArgs>$(AndroidResgenExtraArgs) --no-version-vectors</AndroidResgenExtraArgs>
That would cause the resulting thrice-included command line to be `--no-version-vectors --no-version-vectors --no-version-vectors`, which might *still* be invalid, but isn't ridiculous.
I think you meant to say "which might still be ridiculous, but isn't invalid"
(In reply to Martin Nygren from comment #2)
> I think you meant to say "which might still be ridiculous, but isn't invalid"
Is this still occurring for you with the most recent version of this library? If it's possible, please upload a sample project with this extra argument defined to demonstrate the behavior. This will help us CONFIRM the behavior and ultimately work on a fix for this. Thus I am marking this as NEEDINFO until we have a reproduction project. Otherwise please provide a small set of reproduction steps to minimally reproduce this issue.
It would also be quite helpful for a full diagnostic build output to spot the duplicate args:
Because we have not received a reply to our request for more information we are closing this issue. If you are still encountering this issue, please reopen the ticket with the requested information. Thanks!