Bug 12952 - Have there been recent changes to AOT constraints?
Summary: Have there been recent changes to AOT constraints?
Alias: None
Product: iOS
Classification: Xamarin
Component: XI runtime ()
Version: 4.x
Hardware: Macintosh Mac OS
: --- normal
Target Milestone: Untriaged
Assignee: Bugzilla
Depends on:
Reported: 2013-06-28 20:15 UTC by Adam
Modified: 2016-05-26 11:51 UTC (History)
4 users (show)

Is this bug a regression?: ---
Last known good build:

Failing project (129.95 KB, application/zip)
2013-07-03 02:23 UTC, Adam

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and 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 Links.

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.

Related Links:

Description Adam 2013-06-28 20:15:17 UTC
Im using Catnap ORM - and this exact code was working a week ago.

var sessionFactory = Fluently.Configure
	.ConnectionString("Data source=" + databasePath)
		.DatabaseAdapter(new SqliteAdapter(typeof(Mono.Data.Sqlite.SqliteConnection)))
		.Domain(d =>
			d.Entity<PortfolioPhoto>(e => {
				e.Id( x => x.Id );
				e.Property( x => x.PhotoId );
				e.Property( x => x.SerializedPhoto );

I updated Xamarin (not Catnap), and now this breaks with an error referring to an attempt to JIT code, conflicting with the --AOT flag.

Have there been recent changes to these constraints, because I know nothing has changed on my end - I havent had time to work on my App, and after simply updating Xamarin, and deploying to my iPhone, it no longer works...
Comment 1 Rolf Bjarne Kvinge [MSFT] 2013-07-01 07:15:14 UTC
Would it be possible to get a test case we can use to reproduce it (or even your entire project if that's possible)?

It would also be nice to know which version of Xamarin.iOS you had, and which version you have now.
Comment 2 Adam 2013-07-01 16:43:28 UTC
Sure - I'll zip up a project tonight.

I have 4.0.9 build 12 now - whatever I HAD previously was probably one release version different - I tend to immediately update as soon as it becomes available (thinking about changing that approach though ;)
Comment 3 Adam 2013-07-03 02:23:52 UTC
Created attachment 4263 [details]
Failing project

This is a simple project which fails to run on an iPhone 5 physical device (no problem in simulator) due to AOT constraints.

It fails on Xamarin Studio 4.0.9 (build 12) - but it definitely used to on the previous version (when deployed to same device).
Comment 4 Rolf Bjarne Kvinge [MSFT] 2013-07-03 09:34:05 UTC
Can you get the complete version information from Xamarin Studio's About menu (click on "Show Details" to get the complete information)?
Comment 5 Adam 2013-07-03 16:32:54 UTC
=== Xamarin Studio ===

Version 4.0.9 (build 12)
Installation UUID: 643e75eb-56e8-467d-a793-7a91ad7a306c
	Mono 2.10.12 (mono-2-10/c9b270d)
	GTK 2.24.16
	GTK# (
	Package version: 210120000

=== Apple Developer Tools ===

Xcode 4.6.3 (2068)
Build 4H1503

=== Xamarin.Android ===

Not Installed

=== Xamarin.iOS ===

Version: (Indie Edition)
Build date: 2013-30-05 18:02:40-0400

=== Xamarin.Mac ===

Xamarin.Mac: Not Installed

=== Build Information ===

Release ID: 400090012
Git revision: f9c5c24e88417feb0319953db6d5fc650d416608
Build date: 2013-06-21 17:34:16+0000
Xamarin addins: 898d8afaabb160c025e21656f1490fa149397bff

=== Operating System ===

Mac OS X 10.8.4
Darwin XXXXXXXXX.local 12.4.0 Darwin Kernel Version 12.4.0
    Wed May  1 17:57:12 PDT 2013
    root:xnu-2050.24.15~1/RELEASE_X86_64 x86_64
Comment 6 Sebastien Pouliot 2016-05-24 19:26:01 UTC
The requested info was provided.
Comment 7 Rolf Bjarne Kvinge [MSFT] 2016-05-26 11:51:47 UTC
The test case works fine now, so this was probably fixed some time ago.