Bug 667 - SOAP class instantiation fails in beta
Summary: SOAP class instantiation fails in beta
Alias: None
Product: iOS
Classification: Xamarin
Component: General ()
Version: 4.x
Hardware: Macintosh Mac OS
: --- blocker
Target Milestone: Untriaged
Assignee: Sebastien Pouliot
Depends on: 612
  Show dependency tree
Reported: 2011-09-07 13:48 UTC by joe longo
Modified: 2011-09-07 22:41 UTC (History)
2 users (show)

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

Crash during intantiation of SOAP class which works in previous Mono (6.02 KB, application/msword)
2011-09-07 13:48 UTC, joe longo
Attached Test Case (812.67 KB, application/x-zip-compressed)
2011-09-07 13:49 UTC, joe longo

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 joe longo 2011-09-07 13:48:21 UTC
Created attachment 259 [details]
Crash during intantiation of SOAP class which works in previous Mono

Due to bug 584 needed to update to to get the Sterling engine to work.
Engine now works and app gets farther in, however, now SOAP call fails.
See file Model\GathereSOAPAsync SeecurityGatherer.AuthenticateCredentials method. Fails on line 464 ...target = new ...

This code works in Mono 4.0.7.

Attached crash log.

I am using System.ServiceModel.ClientBase classes created from VS2010's "Add Service Reference..." dialog.
Comment 1 joe longo 2011-09-07 13:49:52 UTC
Created attachment 260 [details]
Attached Test Case
Comment 2 Sebastien Pouliot 2011-09-07 15:07:43 UTC
[0x3efbe48c:] EXCEPTION handling: System.ExecutionEngineException: Attempting to JIT compile method 'System.Linq.Enumerable:FirstOrDefault<System.ServiceModel.Description.OperationDescription> (System.Collections.Generic.IEnumerable`1<System.ServiceModel.Description.OperationDescription>,System.Func`2<System.ServiceModel.Description.OperationDescription, bool>)' while running with --aot-only.

^ this, from your attached log, is also fixed for 4.2 (but after was released). 

However I'm surprised that this worked in 4.0.7 (the same issue was reported there).

I also hit the (just fixed) NRE from bug #612 (which is a regression from 4.0.3). That one is also fixed for 4.2.

To resume I get (using what will be 4.2):


one line at the time when I psuh the "Test SOAP" button on my device.
Comment 3 joe longo 2011-09-07 15:15:35 UTC
How do I get 4.2
Comment 4 Sebastien Pouliot 2011-09-07 15:26:52 UTC
MonoDevelop will offer* the update once available (it needs to be packaged and tested prior to be released).

* you can do it manually with the Help menu, Check for Updates
Comment 5 joe longo 2011-09-07 17:38:29 UTC
is there a separate download location.-
MonoDevelop's download dialog only offers (8-30-2011)Beta
Comment 6 Sebastien Pouliot 2011-09-07 18:24:13 UTC
No, either the automatic (at MD startup) or manual update will only be available once MonoTouch 4.2 is released (i.e. after packaging and testing).
Comment 7 joe longo 2011-09-07 22:41:42 UTC
I found a work-around. I removed the WCF SOAP classes and remplaced them with
SOAP 2.0 classes. I am running the that makes Sterling work and now the
SOAP classes are working.