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 47923 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
I have a Xamarin forms app that uses Vector drawables on Android and PDF vectors inside an asset catalog on iOS.
On iOS I can reference the images fine in both a Xamarin Forms Button (setting the Image property) and an Image (setting the Source property).
On Android I don't see the vector in the Image. I see it in the Button, but it is cropped oddly.
See https://github.com/jimbobbennett/FormsVectorIssue for an app that reproduces this.
See https://github.com/xamarin/Xamarin.Forms/pull/564 (only fixes the Image part)
The poor images could be my converter... Damn you Android and your proprietary image format!
Thanks for fixing the issue. Is there a potential release version?
No idea. It's something that XF team will have to decide. Perhaps it could make it before 2.3.4 stable.
Gonna try pull this for 2.3.5-pre1
Should be fixed in 2.3.5-pre1. Thank you!
On xamarin.form version 184.108.40.2066-pre6 observed that image in button is still cropped oddly.Hence reopening this issue
Screencast link: https://www.screencast.com/t/sgQCan4N
Note: On iOS both images are properly displayed
As mentioned in comment 6, the vector now works as expected for an Image, however the issue with the Button.Image still exists. Therefore I've updated the report title and will keep this report open as confirmed.
Any solution or trick ?? I'm having the same problem in 220.127.116.116-pre6 .