Since upgrading Xamarin Studio, etc., I'm now getting the following exception on the device:
System.ExecutionEngineException: Attempting to JIT compile method '(wrapper delegate-invoke) <Module>:invoke_void__this___object_PropertyChangedEventArgs (object,System.ComponentModel.PropertyChangedEventArgs)' while running with --aot-only. See http://docs.xamarin.com/ios/about/limitations for more information.
In the following method:
public class ViewModelBase : INotifyPropertyChanged
public event PropertyChangedEventHandler PropertyChanged;
protected void Notify(params string propertyNames)
if (PropertyChanged != null)
foreach (var propertyName in propertyNames)
PropertyChanged(this, new PropertyChangedEventArgs(propertyName));
The exception does not occur for all invocations of the method... I have not narrowed down the conditions under which it occurs.
=== Xamarin Studio ===
Version 4.0.10 (build 7)
Installation UUID: d607f156-0fa2-4d15-aeb1-754da529fd97
Mono 3.2.0 ((no/7c7fcc7)
Package version: 302000000
=== Apple Developer Tools ===
Xcode 4.6.3 (2068)
=== Xamarin.Mac ===
Xamarin.Mac: Not Installed
=== Xamarin.Android ===
Android SDK: Not found
=== Xamarin.iOS ===
Version: 220.127.116.11 (Business Edition)
Build date: 2013-30-07 08:24:03-0400
=== Build Information ===
Release ID: 400100007
Git revision: f324e2154ee86ae1b6b8483392eddbf418e6381b
Build date: 2013-07-20 06:23:58+0000
Xamarin addins: fe4f180e2386eafc00087ef68c3a580cff4a2592
=== Operating System ===
Mac OS X 10.8.4
Darwin Jacob-Foshees-MacBook-Air.local 12.4.1 Darwin Kernel Version 12.4.1
Tue May 21 17:04:50 PDT 2013
Can you attach a project we can use to reproduce this?
That's pretty much a perfect test case, thanks.
Zoltan, can you have a look?
Hey guys, thanks for having a look at this. Any update?
We make weekly releases to our stakeholders, and we are blocked until this is resolved... :-(
As a workaround, try not using extension methods as event handlers, i.e.
in the testcase, this seems to trigger the error.
Thanks for the suggested work-around. I've verified that works and we will be able to make a release this week. (-=
Yes, this is still not fixed.
When is this getting fixed? We can't release our updates without big changes on our code. All the code worked before. It is possible to give this bug a higher priority?
Comment #7 might be a different issues that this one. I don't think the original test case in #2 ever worked, and it's pretty hard to fix.
Added the bug as seperate bug: