Bug 18714 - Getting a deprecation error
Summary: Getting a deprecation error
Alias: None
Product: iOS
Classification: Xamarin
Component: Xamarin.iOS.dll ()
Version: 7.2.0
Hardware: Macintosh Mac OS
: --- normal
Target Milestone: Untriaged
Assignee: Bugzilla
Depends on:
Reported: 2014-04-01 14:54 UTC by Ken
Modified: 2014-04-01 16:13 UTC (History)
3 users (show)

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:

Description Ken 2014-04-01 14:54:40 UTC
I'm building an iPad iOS 7.1 application and trying to call


but I'm getting a "Deprecated in iOS 6.1 and OSX 10.8".

When I check the IOS documentation is says it was added not deprecated...
Comment 1 Sebastien Pouliot 2014-04-01 16:13:51 UTC
note: The [Obsolete] should not be an error but a warning.

There was a mistake in Apple documentation that "obsoleted" several NSNetService members. It was half true - what happened is that some "fields" [1] became "properties" and that's not a breaking change (for ObjC or C#). 

Apple corrected this documentation mistake and the obsolete message were removed in monotouch.dll (they are not in 7.2.1). You can search for NSNetService in [2] to confirm it.

[1] Those fields were available well before iOS 6.1.
[2] http://docs.xamarin.com/releases/ios/api_changes/from_7.2.0_to_7.2.1/