Bug 13520 - Error MT2001: Could not link assemblies. Reason: Argument is out of range.
Summary: Error MT2001: Could not link assemblies. Reason: Argument is out of range.
Status: VERIFIED FIXED
Alias: None
Product: iOS
Classification: Xamarin
Component: Tools ()
Version: 6.4.0
Hardware: PC Mac OS
: --- normal
Target Milestone: 6.4.1
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2013-07-26 13:19 UTC by Brendan Zagaeski (Xamarin Team, assistant)
Modified: 2013-09-18 07:49 UTC (History)
6 users (show)

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


Attachments
Screenshot of error in Xamarin Studio (120.22 KB, image/png)
2013-07-26 16:07 UTC, Brendan Zagaeski (Xamarin Team, assistant)
Details
Detailed build logs with -v -v -v mtouch build options (7.71 KB, text/plain)
2013-07-27 05:09 UTC, Ranson Jean-Baptiste
Details


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:
VERIFIED FIXED

Description Brendan Zagaeski (Xamarin Team, assistant) 2013-07-26 13:19:17 UTC
From a user:

I've just upgraded to Xamarin.iOS 6.3.6 and have an MT2001 linker exception.
error MT2001: Could not link assemblies. Reason: Argument is out of range.


[Later, after updating to version 6.4...]

It has appeared since Xamarin iOS 6.3.6. To work-around the issue temporarily, I was not linking any assemblies, so the resulting .ipa was huge.

As soon as I reference Noemax.WCFX.iOS.dll, the problems appears. It is distributed by http://www.noemax.com



## Version information

Xamarin Studio
Version 4.0.10 (build 7)
Runtime:
    Mono 3.2.0 ((no/7c7fcc7)
    GTK 2.24.20
    GTK# (2.12.0.0)
    Package version: 302000000

Apple Developer Tools
Xcode 4.6.2 (2067.2)
Build 4H1003

Xamarin.Mac
Xamarin.Mac: Not Installed

Xamarin.Android
Not Installed

Xamarin.iOS
Version: 6.4.0.2 (Business Edition)
Hash: c9f7659
Branch:
Build date: 2013-18-07 21:36:03-0400
Comment 3 Brendan Zagaeski (Xamarin Team, assistant) 2013-07-26 16:07:33 UTC
Created attachment 4459 [details]
Screenshot of error in Xamarin Studio
Comment 4 Ranson Jean-Baptiste 2013-07-27 05:09:26 UTC
Created attachment 4463 [details]
Detailed build logs with -v -v -v mtouch  build options
Comment 5 Rolf Bjarne Kvinge [MSFT] 2013-07-29 09:02:22 UTC
Fixed.

The bug was that we assume property accessors (in IL) start with "get_" or "set_", which isn't necessarily true with obfuscated assemblies.

monotouch/master-3.0: b14a01acb0cbb07a9438b41b4f13f6a76180706c
monotouch/monotouch-6.4-series: 97bac382f4f4c0feab02135f8ff0cf034214ae76
Comment 6 GouriKumari 2013-07-29 15:53:05 UTC
I could successfully build  the attached testcase without any build errors, with the latest Xamarin.iOS 6.4 build.

BuildOutput: https://gist.github.com/GouriKumari/e9439f00ed27677c23d0

Test Env:

Xamarin Studio
Version 4.0.10 (build 7)
Installation UUID: fafd3486-1aec-4f9c-ab77-08bf4a000708
Runtime:
	Mono 3.2.0 ((no/7c7fcc7)
	GTK 2.24.20
	GTK# (2.12.0.0)
	Package version: 302000000

Apple Developer Tools
Xcode 4.5 (1839)
Build 4G182

Xamarin.iOS
Version: 6.4.0.5 (Trial Edition)
Hash: 94ba87a
Branch: 
Build date: 2013-29-07 12:55:47-0400
Comment 7 Andy 2013-09-10 12:29:20 UTC
Hello,

shouldn't this be fixed ? I get the error with the latest version...
Comment 8 Rolf Bjarne Kvinge [MSFT] 2013-09-18 07:49:57 UTC
Andy: the error is fairly generic, so it's likely you're hitting a different issue. Please open a new bug with a test case and we'll look at it.