Bug 7381 - CLLocationManager.UpdatedLocation event should show as obsolete and break in debugger
Summary: CLLocationManager.UpdatedLocation event should show as obsolete and break in ...
Status: RESOLVED DUPLICATE of bug 7882
Alias: None
Product: iOS
Classification: Xamarin
Component: Xamarin.iOS.dll ()
Version: 6.0.x
Hardware: Macintosh Mac OS
: --- normal
Target Milestone: Untriaged
Assignee: Bugzilla
Depends on:
Reported: 2012-09-21 10:14 UTC by Neal
Modified: 2012-10-18 08:18 UTC (History)
2 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 Neal 2012-09-21 10:14:53 UTC

First and foremost THANK YOU for the outstanding and timely iOS 6 support.  Kudos to all of you!!!

I found CoreLocation among other things changed in iOS 6, this one took me a while to figure out.  My app's min target is set to 6.0 and I used the line of code below in iOS 5 which works:

LocationManager.UpdatedLocation += HandleUpdatedLocation;

As you know in iOS 6 "UpdatedLocation" is now changed to use LocationsUpdated.

I would have expected with Min OS set to 6.0 that "UpdatedLocation" should have been caught by the compiler and should have raised an exception when running/debugging.  You may want to look into this, i.e. is a binding available from iOS 5 that shouldn't be with iOS 6.0 as the target?

Thanks again!

P.S.  It would be helpful to us if all of your samples/recipes/tutorials that required an update for iOS 6 - if we could have a list of everything that needed an update.  If I had known CoreLocation (in your Navigation recipes) required an update it would have clued me in as to something I needed to change.  I am not as knowledgable as you all as to everything that changed in iOS 6 and requires recoding, CoreLocation was not addressed in the iOS 6 intro/doc pages with other things that changed.
Comment 1 Rolf Bjarne Kvinge [MSFT] 2012-10-18 08:18:00 UTC
We'll warn for the obsoleted event in MonoTouch 6.0.5.

There weren't that many breaking changes in iOS6 (I believe this is the most often encountered actually) - in any case here you can see the list of commits for the samples: https://github.com/xamarin/monotouch-samples/commits/master - admittedly this information is not very easy to find.

*** This bug has been marked as a duplicate of bug 7882 ***