Latest Contributions by dotMorten_esri

No problem. You're fine to continue using the old ones until the next major release. The new classes are mostly there because we're working towards a common authentication codebase used across all the maps sdk platforms to improve consistency, faster improvements and only having to make fixes in one place (Swift and Kotlin SDKs already use it). That common underlying codebase is slightly different / modernized and we're building the design to match that before fully switching over in the next major release and removing the deprecated classes. So as long as you move over before that switch, you'll be fine. ... View more

There property is in the namespace: `Esri.ArcGISRuntime.Controls.UI.SceneView` Make sure you place the code inside an #if __ANDROID__ section since the specific property is only available on the Android target. ... View more

We could probably improve that error message a bit to make it more clear. I'll put that in the backlog. ... View more

Something like this should work:     private static string GetDisplayValue(Field field, Feature feature) { if (field is null || feature is null || !feature.Attributes.ContainsKey(field.Name)) return string.Empty; var value = feature.Attributes[field.Name]; if (field.Domain is CodedValueDomain cvd) { value = cvd.CodedValues.FirstOrDefault(c => c.Code == value)?.Name ?? value; } return value?.ToString() ?? string.Empty; }   ... View more

Unfortunately the Android platform makes implementing the scenario a lot harder and has to be done at the application level with the foreground service. There's not much we can really do at the API level, besides improving our documentation to help implement this. ... View more

We're working on a sample/tutorial/doc to help with this scenario. But take a look at Android's doc on this, especially foreground service (keeps app open in the background): https://developer.android.com/develop/background-work/services/fgs and background services: https://developer.android.com/develop/sensors-and-location/location/background (runs while app isn't running) ... View more

We've recently been made aware of a regression with older 32bit Android Armv7 devices and are still investigating, and it appears you're likely also hitting this. We're still trying to fully determine if this is an issue in the .NET runtime or the Maps SDK (it was introduced in 200.5, because of some newer code hitting this .NET bug). ... View more

You are correct there's no event like this currently. You could use the GeoViewTapped event and compare the location of the tapped event to the location of the location display. I'd recommend using the screen location of the click event and convert the locationdisplay location to screen coordinates using MapView.LocationToScreen(location), so you can calculate in pixels how far away from the location the click was, and you can just set a threshold of the size of the symbol. This is all a pretty cheap calculation to make so shouldn't cause any overhead. Something along the lines of( (not tested):   private void MapView_GeoViewTapped(object sender, GeoViewInputEventArgs e) { if ((sender as MapView)?.LocationDisplay?.Location?.Position is MapPoint location) { var screenLocation = mapView.LocationToScreen(location); var distance = Math.Sqrt(Math.Pow(e.Position.X - screenLocation.X, 2) + Math.Pow(e.Position.Y - screenLocation.Y, 2)); if (distance < 12) { // You clicked location } } }   ... View more

You can use the HorizontalAccuracy property of the location to check if you're getting a bad measurement and ignore it. ... View more