I created a simple UWP application with no code, just XAML.
<
One of the maps services was returning bad data. This has been mitigated and the control should be working normally now.
I made a test for this. The sample works correctly in Build 2004 but it crashes in Build 20H2. If I remove the code that changes the ZoomLevel property, the sample will work correctly in Build 20H2 as well. I'll report this to the team.
This is the support response I got from Microsoft:
Upon investigation, the Bing Maps UWP control was inadvertently unable to handle a certain condition around the tiles. To mitigate this issue, our Product Group has initiated rolling back the change that impacted this experience. This issue should be beginning to resolve within the next hour, if not already.
This issue is now resolved.
I am facing exactly same issue. I have been testing my application for the last 2 months and it never crashed because of MapControl. I submitted the application on the store last week and yet no crash.
Suddenly, it started crashing today whenever the user navigated to map page containing PivotControl for different weather layers.
I don't think this has anything to do with Windows 10 build. I am facing this issue across multiple builds (1803, 1903 & 2004).
Here are my few observations.
It seems that Microsoft has changed something at the service end.
This happens to me also, it was just working fine yesterday and today the app is crashing when opening the page with the MapControl on it. Removing the ZoomLevel property helped.
<maps:MapControl ZoomLevel="12" /> <!-- Crashed -->
<maps:MapControl /> <!-- Working -->
Removing the ZoomLevel property but zoom in manual (or with mouse scrolling) the app is crashing while zooming in to far.
Temporary workaround:
<maps:MapControl ZoomInteractionMode="Disabled" /> <!-- Better -->
Happens on Windows 10 Build 2004 also.