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.
Keeps throwing a build error of:
Error Failed to resolve "Xamarin.Forms.ImageSource Xamarin.Forms.ImageSource::FromResource(System.String)" reference from "Xamarin.Forms.Core, Version=188.8.131.52, Culture=neutral, PublicKeyToken=null" MyApp.iOS
Could you possibly provide a reproduction and any other pertinent information?
Doing a clean and rebuild seems to have fixed the error:
Although I have a strong feeling something has happened to ImageSource.FromResource that may need investigating.
I don't know if you have access to Syncfusion Datagrid but if you use this with Xamarin.Forms V2 It throws a missing method exception on Android.
Missing method ImageSource.FromResource.
I'm going to close this particular issue for now
I checked with Syncfusion and the Android bug mentioned here is due to their datagrid referencing Forms V1.5.1 and the descrepency in the ImageSource class
They have now clarified this so this bug is invalid
I would like clarify that this is not a Syncfusion bug.
In DataGrid control we have used ImageSource in the business logics. Since your reported version of Syncfusion controls supports 1.5.1 version of Xamarin, upgrading your sample to XF 2.0 lead to the issue.
This could even be reproduced in a simple scenario and has already been reported here.
Xamarin suggest making sure that the versions of Forms are aligned correctly in order to avoid potential issues, hence this is a Xamarin issue.
Worth noting: In Forms 184.108.40.20671 this compiles but crashes the app; in 220.127.116.1105 the compiler catches it and it will not build, as noted at the top.