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 56816 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
VS 2017 15.2
I had a stray char (6 after the last RowDefinition) that should be a syntax error in my XAML. Would compile fine for UWP and iOS, but caused a runtime KeyNotFoundException when the XAML was loaded.
I would expect this to cause a compile time error?
I tested this and there is a build error thrown when XamlC is enabled: https://developer.xamarin.com/guides/xamarin-forms/xaml/xamlc/
However the error that gets thrown is
> Error: Specified cast is not valid.
with no additional information to help indicate what caused it. Therefore I'll still confirm this report so that we can try to improve the error thrown in the future.
I'll check that, it's possible this was an older XAML page, it might not have had XamlC enabled on it.
I could be helpful if the KeyNotFoundException could include the key that is missing also. Would make it easier to track it down.