Fody v2.3.1 breaks Xamarin.Forms
See original GitHub issueWhile I haven’t been able to track down the main reason causing the issue, v2.3.0 and below work fine, while v2.3.1 causes a rather nasty (and hard to track down) exception to be caused when used with Xamarin.Forms:
Error MSB4018: The "XamlCTask" task failed unexpectedly.
System.InvalidOperationException: Operation is not valid due to the current state of the object.
I’m more interested in what changed between v2.3.0 and v2.3.1 and if the upcoming v2.3.2 will fix it.
Issue Analytics
- State:
- Created 6 years ago
- Comments:6 (4 by maintainers)
Top Results From Across the Web
ArgumentNullException when using both ...
@tuyen-vuduc I have upgraded an app to use Realm 3.1 and Fody 3.1.3 without any issues, at least on iOS. However, I'm not...
Read more >Xamarin Forms Android app is not working through ...
The app gets an error that the host is unknown while connecting to a url that the split tunnel should consider as internal....
Read more >Xamarin Forms with localization strings not shown in XAML ...
String will be empty in XAML Preview, making it's impossible to design further without actually running emulator to check it everytime. Visual Studio...
Read more >UIWebView Deprecation and Xamarin.Forms
This would potentially break custom renderers or other code that referenced this class implemented by Xamarin.Forms users.
Read more >Could not load assembly 'Telerik.XamarinForms.SkiaSharp
Hi All, I have installed a licensed version of Telerik.XamarinFroms.UI and can`t build my project.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
ok sorry about the hassle. on my next release i will add Xamarin.Forms to my list of smoke tests.
Can confirm that 2.3.2 does indeed fix it!