Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
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
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 for Bug 30611 on
GitHub or Developer Community if you have new
information to add and do not yet see a matching new report.
If the latest results still closely match this report, you can use the
In special cases on GitHub you might also want the comments:
GitHub Markdown with public comments
Got a weird problem after latest upgrade of Mono/Xamarin studio on MAC OSX.
A SOAP Proxy that used to work just fine now gives the following error:
"System.InvalidProgramException: Invalid IL code in System.Web.Services.Protocols.SoapHttpClientProtocol:Invoke (string,object): IL_0000: ret \n\n\n at MagentoSOAP.MagentoService.login (System.String username, System.String apiKey) [0x00015] in /Users/morten/dev/projects/mono/warehouseintegration/src/WarehouseIntegration/Shopintegrations/Magento/src/MagentoSOAP/MagentoService.cs:800 \n at (wrapper remoting-invoke-with-check) MagentoSOAP.MagentoService:login (string,string)\n
Checked parameters of the method, no problem there.
Oh my, this is bad for my deadline..
Any ways to downgrade to a previous version ?
The proxy used generated was generated using the wsdl tool.
I tried generating it again after the update of Xamarin studio, but with same result.
A clue to solving:
Finally I upgraded the project with the soap proxy to mono 4.5. and the the error disappeared.
But I cannot consider that as a solution because other projects that are dependent on the proxy are running mono 4.0 in a production environment.
Unfortunately this latest Xamarin studio update (5.9.1 build3) seems a bit too broken, so I will try going back to the previous version, which was a very nice job, and I may be unable to provide anymore info.