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 51563 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
Created attachment 19359 [details]
Description of Problem:
Exception is thrown when effect is applied to Editor on iOS
Steps to reproduce the problem:
1.Create a new XF project
2.Add an Editor component
3.make an effect
4.apply the effect
5.start the app
Editor with effect applied
How often does this happen?
Xamarin Forms 126.96.36.199
Thanks for filing the report. It appears to be an exception in the Xamarin.Forms code, so I've reassigned it to that team.
Having the same issue using Beta Channel
Customer expects the message of unhandled exceptions to be shown if a debugger is attached. What actually happens is the app hangs (sometimes it'll issue a generic exception message tho I cannot reproduce reliably).
Throwing a try/catch around the body of EditorEffectAppPage.ctor will catch an exception with the message:
Xamarin.Forms.Xaml.XamlParseException: Position 9:5. Cannot assign property "Effect": Property does not exists, or is not assignable, or mismatching type between value and property
This message should be displayed after removing the try/catch.
In this case, changing the name "Effect" to "Effects" will prevent the exception.
I fixed the hang for 15.3, but I need to reassign this to Runtime for never actually returning the proper exception message.
UE capture in the products doesn't depend on the runtime, shipping to the SDK team.