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.
Created attachment 12456 [details]
Test case exhibiting broken JSExport
Exporting methods to JSC that do not take any arguments works as expected.
Similar blocking behavior can be seen with the following, one of which is likely the underlying culprit for the JSExport invocation blocking:
- JSValue.From (NSObject, JSContext)
- JSValue.ToObject ()
Attached is a Xamarin.Mac sample that likely requires the latest Xamarin.Mac and Xamarin Studio from master (since it uses storyboards instead of xibs).
When running the sample, clicking the "Working" button should print the JS mouseEvent object to the console. Clicking "Broken" will block the application indefinitely (pinwheel of doom).
*** This bug has been marked as a duplicate of bug 32511 ***
To see the meat of the test case code without having to download the whole project: