Unexpected Error with MapRouteFinder in UWP App

Thanks for your prompt response, Harry.

I appreciate you looking into the code. My apologies – I only provided a snippet earlier to highlight the section where we're encountering the error. The item variable is declared and used correctly within the full loop.

We've actually been using the documentation you linked as a reference during development, and our business logic was built upon it. The implementation has been working without issues for quite some time, and without any changes on our end, we've recently started receiving errors specifically from the GetDrivingRouteFromEnhancedWaypointsAsync method.

We've also noted the recent announcement regarding Bing Maps shifting support towards Azure Maps. We're wondering if there might have been a change in the native API request or response structure within the Windows.Services.Maps library's methods that could be causing this sudden issue.

Could this be a possibility?

var LocationList =new List<Customer>(){
new Customer {Name="C1",Latitude=42.029832, Longitude=-87.683389},
new Customer {Name="C2",Latitude=41.92209, Longitude=-87.64922},
new Customer {Name="C3",Latitude=41.903669, Longitude=-87.65712},
new Customer {Name="C4",Latitude=41.889947, Longitude=-87.630301}
};
BasicGeoposition point1 = new BasicGeoposition() { Latitude = 
42.029858
BasicGeoposition point2 = new BasicGeoposition() { Latitude = 
42.029858
var StartGeopoint=
var EndGeopoint=
var path = new List<EnhancedWaypoint>();
path.Add(new EnhancedWaypoint(StartGeopoint, WaypointKind.Stop));
for (int index = 0; index < LocationList.Count; index++) {         
BasicGeoposition point = new BasicGeoposition() { 
Latitude = item.Latitude, Longitude = item.Longitude };         
path.Add(new EnhancedWaypoint(new Geopoint(point), WaypointKind.Via)); 
}
path.Add(new EnhancedWaypoint(EndGeopoint, WaypointKind.Stop));

Hi @Lokender Tiwari ,

Thank you for the clarification!

After reviewing your code again, I can confirm that you're correctly using EnhancedWaypoint with the appropriate WaypointKind.Stop and Via values. Despite that you're already confirm the item variable is declared and used correctly, I still did not see it defined in the snippet. I'm sorry to mention it again but I just wanted to double-check in case that's contributing to the issue.

Since you've confirmed the code worked well in the past and only recently started failing, the issue may be from something outside your application logic, possibly related to a silent failure in the routing service causing the API to return an "Unspecified error".

You can try using MapRouteFinderStatus to debug logging so we can detect the issue:

var result = await MapRouteFinder.GetDrivingRouteFromEnhancedWaypointsAsync(path); 
if (result.Status != MapRouteFinderStatus.Success) 
{     
	Debug.WriteLine(result.Status); 
}

This can help determine whether the failure is due to NoRouteFound, NetworkFailure, or some other specific cause. There are 10 possible results, and you can read here for more detail.

Can you also test with just a start and end point — without any Via waypoints to see if it works with simpler path:

var path = new List<EnhancedWaypoint>
{
    new EnhancedWaypoint(StartGeopoint, WaypointKind.Stop),
    new EnhancedWaypoint(EndGeopoint, WaypointKind.Stop)
};

Let me know the result of these checks. I hope these will help you detect your problem! Thank you!

Hi @Harry Vo (WICLOUD CORPORATION) ,

Thanks for the follow-up! I tried the snippet you suggested, and it works perfectly.

var path = new List<EnhancedWaypoint>
{
    new EnhancedWaypoint(StartGeopoint, WaypointKind.Stop),
    new EnhancedWaypoint(EndGeopoint, WaypointKind.Stop)
};

As soon as I introduce a single WaypointKind.Via for example (42.029832,-87.683389) between the start and end waypoints, the code throws an "Unexpected Error" when calling GetDrivingRouteFromEnhancedWaypointsAsync. This error prevents any response from being captured in the result variable.

var result = await MapRouteFinder.GetDrivingRouteFromEnhancedWaypointsAsync(path); 
if (result.Status != MapRouteFinderStatus.Success) 
{     
	Debug.WriteLine(result.Status); 
}

Hi @Lokender Tiwari , thank you for your update, and I very appreciate you test my simplified case!

Based on your result, it's clear that it works correctly with Stop waypoints, but fails when a Via waypoint is added - which strongly suggests this is an issue at the API/service level, not within your application logic.

There’s one last thing I’d like you to try based on this documentation. Please test this snippet in your project, and if possible, in a blank project.

using System;
using Windows.Devices.Geolocation;
using Windows.Services.Maps;
using Windows.UI;
using Windows.UI.Xaml.Controls;
using Windows.UI.Xaml.Controls.Maps;
...
private async void ShowRouteOnMap()
{
  Geolocator locator = new Geolocator();
  locator.DesiredAccuracyInMeters = 1;
  locator.PositionChanged += Locator_PositionChanged;
  BasicGeoposition point1 = new BasicGeoposition() { Latitude = 47.649693, Longitude = -122.144908 };
  BasicGeoposition point2 = new BasicGeoposition() { Latitude = 47.6205, Longitude = -122.3493 };
  BasicGeoposition point3 = new BasicGeoposition() { Latitude = 48.649693, Longitude = -122.144908 };
  // Get Driving Route from point A  to point B thru point C
  var path = new List<EnhancedWaypoint>();
  path.Add(new EnhancedWaypoint(new Geopoint(point1), WaypointKind.Stop));
  path.Add(new EnhancedWaypoint(new Geopoint(point2), WaypointKind.Via));
  path.Add(new EnhancedWaypoint(new Geopoint(point3), WaypointKind.Stop));
  MapRouteFinderResult routeResult =  await MapRouteFinder.GetDrivingRouteFromEnhancedWaypointsAsync(path);
  if (routeResult.Status == MapRouteFinderStatus.Success)
  {
      MapRouteView viewOfRoute = new MapRouteView(routeResult.Route);
      viewOfRoute.RouteColor = Colors.Yellow;
      viewOfRoute.OutlineColor = Colors.Black;
      myMap.Routes.Add(viewOfRoute);
      await myMap.TrySetViewBoundsAsync(
            routeResult.Route.BoundingBox,
            null,
            Windows.UI.Xaml.Controls.Maps.MapAnimationKind.None);
  }
}

Since this appears to be a backend regression and there's unfortunately nothing we can address from your side at the moment, if you still encounter the same issue from the snippet above, I suggest that you might need to open a support ticket for further investigation. Please kindly note that your support ticket will be free if it is Microsoft's issue.

Also, please make sure your Bing Maps key is up to date, as an expired or invalid key can cause unexpected issues. Existing free (Basic) account customers can continue to use Bing Maps for Enterprise services until June 30th, 2025, so make sure you are using enterprise account! (You can read more at Home page of Bing Maps Portal)

I'm sorry I couldn't solve your problem. Bing Maps isn't my area of expertise, and it's currently reaching the end of its support (click here to learn more). I recommend switching to Azure Maps for long-term support, you can read this documentation for more detail! Thank you!

(Duplicated comment)