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 for Bug 57270 on
Developer Community or GitHub if you have new
information to add and do not yet see a matching new report.
If the latest results still closely match this report, you can use the
In special cases on GitHub you might also want the comments:
GitHub Markdown with public comments
Created attachment 22773 [details]
PCL UWP demo project
This bug repo highlights three issues that exist in the UWP map renderer
1) If you change the map marker icon in the renderer the existing marker icon remains although the new asset is shown also, intermittent since 2.3.3 when we 1st wrote this renderer.
2) The mapspan is been ignored (appeared in 2.3.4)
3) If you rotate the map the app crashes, comment out the following line in the renderer:
_nativeMap.RotateInteractionMode = MapInteractionMode.Disabled;
Tested on Nokia Lumia 650, OS build 10.0.15063.297
Windows SDK: 10.0.14393.0
As it stands the map control is pretty unusable for us in UWP at present.
Hey Norman, thanks for filing this! I was able to reproduce all three issues with 18.104.22.168.
Fortunately I did notice some improvements when testing with 2.3.5-pre3:
- The rotation crash seems to be resolved
- The MapSpan seems to now work intermittently
As for the map marker issue, I think what is happening is that unlike on iOS or Android, if multiple markers are placed at the same coordinates in the UWP they will all be visible instead of only the topmost.
However I'm not sure if this is a platform issue or something we can fix on our end. But in the meantime, a quick workaround for this is to only add the pin to your custom pin collection and _not_ the Forms Map collection on UWP. This will prevent the default pin from being added to the control.
I'll confirm this report so we can look further into the map span and marker issues. Thanks!
Thanks for the custom pins tip, I can confirm that resolves the duplicate marker issue.
The mapspan is the main blocking issue now.
I can confirm I'm seeing better results with mapspan in 2.3.5 pre3.