nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Access violation when routing with offline map

RobrechtUlens

Hello,

When creating MapPoints to define stops for a route, I was under the impression that these would accept longitude and latitude coordinates. I tried to calculate a route using these coordinates and my application had a hard crash due to an access violation.

I figured out that I could convert from longitude latitude to mappoints using CoordinateFormatter.FromLatitudeLongitude(). This has solved my issue. I guess before it was trying to route between points that were not in the offline map package I was using.

I thought I would let you know about this hard crash. Attached is a project that reproduces the issue. I am using 100.5.0 of the .NET SDK and I'm using the belgium.mmpk map which I downloaded from https://developers.arcgis.com/downloads/streetmap-premium-for-runtime. I also tried the 100.4.0 .NET SDK and got the same problem.

Kind regards,

Robrecht

ArcGISApp1_repro.zip

Find more posts tagged with

Accepted answers

RobrechtUlens

Hi Michael Branscomb‌

The issue is no longer reproducible with version 100.6.0 of the SDK.

Thanks,

Robrecht

All comments

MichaelBranscomb

Hi,

Thanks for confirming.

Cheers

Mike

RobrechtUlens

Hi Michael Branscomb‌

The issue is no longer reproducible with version 100.6.0 of the SDK.

Thanks,

Robrecht

MichaelBranscomb

Hi,

This issue requires further investigation to determine the cause of the error and the appropriate resolution.

In the interim you can workaround this by specifying the SpatialReference of the Stop geometries you are creating:

e.g.

`List<MapPoint> coordinates = new List<MapPoint> { new MapPoint(50.9208595, 5.3386841,SpatialReferences.Wgs84), new MapPoint(50.9299484, 5.3944303,SpatialReferences.Wgs84) };`

These specific coordinates will cause the SolveRouteAsync task to return an exception that you can catch. The exception message indicates that the Stops cannot be located on the network.

Cheers

Mike

MichaelBranscomb

Hi,

Thanks for the straightforward repro case. I've open an issue in our backlog and we'll investigate.

Cheers

Mike

Join the Conversation

Signed in members can post, follow updates, and more. New here? Register a free account.

Quick Links

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.