Bug 13249 - AOT with the latest xamarin updates from the alpha channel (xamarin.ios 6.3.7.164)
Summary: AOT with the latest xamarin updates from the alpha channel (xamarin.ios 6.3.7...
Status: RESOLVED NORESPONSE
Alias: None
Product: iOS
Classification: Xamarin
Component: Tools ()
Version: 6.9.3.x
Hardware: PC Mac OS
: --- normal
Target Milestone: Untriaged
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2013-07-15 09:18 UTC by Lucian Torje
Modified: 2013-12-05 18:34 UTC (History)
2 users (show)

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

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:
Status:
RESOLVED NORESPONSE

Description Lucian Torje 2013-07-15 09:18:00 UTC
With the latest monotouch, compiling the code with "Don't link" leads to "Could not AOT the assembly '....Core.dll'"

Using http://download.xamarin.com/MonoTouch/Mac/monotouch-6.3.6.77.pkg and the same code + static libraries, the problem disappears.

=== Xamarin Studio ===

Version 4.1.6 (build 2)
Installation UUID: 480641ea-25a7-4d52-8b33-04edae97af3a
Runtime:
	Mono 3.0.12 ((no/d6c5db8)
	GTK 2.24.18
	GTK# (2.12.0.0)
	Package version: 300120000

=== Apple Developer Tools ===

Xcode 4.6.3 (2068)
Build 4H1503

=== Xamarin.Mac ===

Xamarin.Mac: Not Installed

=== Xamarin.Android ===

Version: 4.7.11 (Business Edition)
Android SDK: /Users/lucian/Library/Developer/Xamarin/android-sdk-mac_x86
	Supported Android versions:
		2.1   (API level 7)
		2.2   (API level 8)
		2.3   (API level 10)
		3.1   (API level 12)
		4.0   (API level 14)
		4.0.3 (API level 15)
		4.1   (API level 16)
		4.2   (API level 17)
Java SDK: /usr
java version "1.6.0_51"
Java(TM) SE Runtime Environment (build 1.6.0_51-b11-457-11M4509)
Java HotSpot(TM) 64-Bit Server VM (build 20.51-b01-457, mixed mode)

=== Xamarin.iOS ===

Version: 6.3.6.77 (Business Edition)
Hash: fa63be7
Branch: 
Build date: 2013-17-06 20:54:24-0400

=== Build Information ===

Release ID: 401060002
Git revision: dc82b708c19d7fa1dc3ad314cc6daf2151813130
Build date: 2013-07-11 20:50:47+0000
Xamarin addins: 97527c853b2a4f05cc024e3109368091be7f9d4f

=== Operating System ===

Mac OS X 10.8.4
Darwin Lucians-MacBook-Pro.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 1 Sebastien Pouliot 2013-07-15 14:38:15 UTC
We'll need more information: at the very minimum a full build log (and likely more, like a test case).

Note that using "Dont link" for device builds is not recommended: neither for development (it's too slow to build an deploy) nor for releases: it creates huge* apps.

* at some point they can get too big for the compiler to process (24 bits limitation) or the whole applicaiton native binary size will go over 60MB and Apple will reject it (for the appstore).
Comment 2 PJ 2013-11-19 17:04:21 UTC
This bug has been in the NEEDINFO state with no changes for the last 90 days. Can we put this back into the NEW or CONFIRMED state, or are we still awaiting response?

If there is no change in the status of this bug over the next two weeks, this bug will be marked as NORESPONSE.
Comment 3 PJ 2013-12-05 18:34:23 UTC
This bug has not been changed from the NEEDINFO state since my previous comment, marking as RESOLVED NORESPONSE.

Please feel free to REOPEN this bug at any time if you are still experiencing the issue. Please add the requested information and set the bug back to the NEW (or CONFIRMED) state.