Reverse Geocoding Not Behaving As Expected In 200.6/ArcGIS Pro 3.4

KyleGruber — Tue, 05 Aug 2025 15:55:01 GMT

I have an app using .NET Runtime SDK 200.6 for WPF and a MobileMapPackage with a locator created using ArcGIS Pro 3.4. When I do a reverse geocode on an address point, I'm no longer getting the individual location elements (StPreDir, StName, etc) despite using the following code.

var userLocation = MainMap.APSSMapView.ScreenToLocation(e.Position);
ReverseGeocodeParameters p = new ReverseGeocodeParameters();
p.ResultAttributeNames.Add("*");
p.OutputSpatialReference = MainMap.APSSMapView.SpatialReference;
var closest = await MainMap.BaseMap.LocatorTask?.ReverseGeocodeAsync(
    userLocation, p);

I only get the following attributes:

Typically, this is something that ResultAttributeNames.Add("*") has fixed. Anyone have any ideas?

Here is what the same locator result looks like in ArcGIS Pro, which is what I'm expecting:

Re: Reverse Geocoding Not Behaving As Expected In 200.6/ArcGIS Pro 3.4

dotMorten_esri — Thu, 14 Aug 2025 16:39:28 GMT

I'm curious: Does it work if you instead of using *, add all the missing field names to the list? I'm curious if it's a bug wrt using *, or if the data just isn't being made available for whatever reason.

topic Re: Reverse Geocoding Not Behaving As Expected In 200.6/ArcGIS Pro 3.4 in .NET Maps SDK Questions

Reverse Geocoding Not Behaving As Expected In 200.6/ArcGIS Pro 3.4

Re: Reverse Geocoding Not Behaving As Expected In 200.6/ArcGIS Pro 3.4