AnsweredAssumed Answered

Access Violation In Runtime 100.5 With Composite Locator Containing New Locator

Question asked by NimbusHex on Apr 10, 2019
Latest reply on Jul 5, 2019 by MBranscomb-esristaff

I'm getting an Access Violation in runtimecore.dll when calling SuggestAsync on LocatorTask (ArcGIS Runtime 100.5).  This is a composite address locator comprised of 3 Street Address locators embedded in a mobile map package (created with ArcGIS Pro 2.3.2).


What I'm trying to accomplish is less strict enforcement of the address suggestion/geolocation when it comes to pre/post directions and suffixes.  For example, if the user enters "100 MAIN", I would like the suggestions to include 100 E MAIN ST if it exists.  I have not found a way to accomplish this with a single locator, so instead I stacked locators in a composite (first one contains all elements, second one removes pre/post directions, third one further removes suffix).  If there is a better way to accomplish this, I would certainly be open to hearing it.


A sample project with this issue can be downloaded here:


Note:  Just in case it's not obvious, to reproduce the issue type anything in the textbox in the upper-left corner.