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 4330 [details]
I'm running into an issue where async code is throwing a JIT exception when running on a device. If I remove some of the levels of async/await nesting it seems to help avoid the exception, so I'm hoping this is a runtime bug rather than an iOS limitation. Attached is a repro case for the crash.
Xamarin.iOS Version: 126.96.36.199 (Business Edition)
Mono 3.0.12 ((no/d6c5db8)
2013-07-11 18:29:26.863 JitTest[45423:907] Unhandled managed exception: Attempting to JIT compile method 'JitTest.JsonRestClient:makeRequestAsync<JitTest.Person> (string)' while running with --aot-only. See http://docs.xamarin.com/ios/about/limitations for more information.
at JitTest.JsonRestClient.GetAsync[Person] (System.String url) [0x00000] in <filename unknown>:0
at JitTest.JitTestViewController+<ViewDidLoad>c__async0.MoveNext () [0x00038] in /Users/greg/Projects/JitTest/JitTest/JitTestViewController.cs:28
As a workaround, ry calling the async method directly instead of through GetAsync().
This works now with mono 5e9f57b92f25e0cd0fef266cb713c54289c95c86.
Is there a target for when this will reach Xamarin.iOS? I'm still getting this exception on 6.4.0.
That fix didn't made 6.4.0.
Hate to be a pain, but is there a timeline yet on when this will make it into iOS/Android? This is a pretty big stopper for us at the moment. Thanks!
This was fixed a long time ago.