Bug 35605 - The overload of Polygon in MapBox component does not accept an array of co-ordinates
Summary: The overload of Polygon in MapBox component does not accept an array of co-or...
Status: RESOLVED FIXED
Alias: None
Product: Components
Classification: Xamarin
Component: Xamarin Components ()
Version: Production (addons.xamarin.com)
Hardware: Macintosh Mac OS
: --- normal
Target Milestone: ---
Assignee: Jon Dick
URL:
Depends on:
Blocks:
 
Reported: 2015-11-05 19:00 UTC by k.a.shah
Modified: 2015-12-01 16:05 UTC (History)
1 user (show)

Tags:
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:
Status:
RESOLVED FIXED

Description k.a.shah 2015-11-05 19:00:48 UTC
As per https://www.mapbox.com/ios-sdk/examples/polygon/ the polygon object accepts an array of co-ordinates. 

When you see the corresponding Xamarin implementation you have an overload accepting only one co-ordinate:


[Export ("polygonWithCoordinates:count:"), CompilerGenerated]
public static Polygon WithCoordinates (CLLocationCoordinate2D coords, nuint count);
Comment 1 Jon Dick 2015-12-01 16:05:40 UTC
This will be fixed in the 3.0.0 release of the component (fixed in xamarin/components/master by 7e50f319bf)

The problem was that the coordinates parameter should have been an array instead of a single instance.