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.
MKLocalSearchRequest is intended to have a constructor that accepts an MKLocalSearchCompletion, so you can easily go from autocomplete results to results you can place on a map.
I notice that such a constructor is described here, in the MonoTouch.MapKit API: https://developer.xamarin.com/api/type/MonoTouch.MapKit.MKLocalSearchRequest/
However, it's not present when I go to use it in code. I'm seeing only the default constructor, as described in this API:
I'm in a PCL 4.5 Profile111 project, and my iOS project is targeting version 9.3.
Is there some way to access the appropriate constructor, or a workaround that I can use? For the time being, I'm simply concatenating the MKLocalSearchCompletion's Title and Subtitle properties into the NaturalLanguageQuery property of an MKLocalSearchRequest after creation.
Did some investigation in Xcode on a native project and it seems all that constructor does is the same thing my workaround is doing already...concatenates the Title and Subtitle with a space in between, and sets that to the NaturalLanguageQuery.
So, I'll leave the bug as it seems that constructor should still be implemented, but it's no longer feeling like a priority request :)
Good catch! It looks like is was only added for classic (not unified) with XI 9.6 / iOS 9.3 support . Git history don't tell why nor do I recall (I did add the API) but I suspect I copy-pasted the !MONOMAC condition (and picked up the !XAMCORE_2_0 withit)
PR master https://github.com/xamarin/xamarin-macios/pull/1832
The steps are missing in this bug so can you provide steps for verify this bug.
@Roshan, there's no need to verify this bug, it's just an API addition.