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 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.
Description of Problem:
I have a Web Service created in VS2012 that runs on IIS. It works fine with Delphi client or C# client, but Xamarin.iOS project throws InvalidOperation Exception:
Member AbcAuthHeaderValueField not found in class GrandFeast.MenuTouch.iOS.DataAsyncServiceReference.DataSyncService.
var url = String.Format(URL_DATASYNC_SERVICE, WEB_SERVICE_IP);
var dataAsyncService = new DataSyncService(url); // Exception throws.........................
this.Url = "http://192.168.1.200:2014/WebServices/DataSyncService.asmx";
public DataSyncService(string url) // Exception throws.......................................
this.Url = url;
public AbcAuthHeader AbcAuthHeaderValue
this.AbcAuthHeaderValueField = value;
Steps to reproduce the problem:
How often does this happen?
Thanks so much for taking the time to submit this report! I’m unable to reproduce this issue using the latest Xamarin.iOS 10.12.0.14. Please attach the following to help us reproduce this issue:
- Detailed reproduction steps
- Visual Studio Version information (About Visual Studio menu)
- project to reproduce your issue
- Full exception message and stack trace.
We have not received the requested information. If you are still experiencing this issue please provide all the requested information and re-open the bug report. Thanks!