Release notes for 200.4

This page provides details about enhancements in the 200.4 release of ArcGIS Maps SDK for .NET. It also lists this release's deprecations, resolved issues, known issues, and more.


The following enhancements have been added with this release.



The GeometryEditor now supports feature snapping when interactively creating and editing geometries. Snapping allows you to create geometries that connect and are coincident, so that interactive edits are more accurate, with fewer errors. When snapping is enabled in the SnapSettings, visual cues indicate to the user when edits have snapped to features. See SnapSource for information about configuring layers to be valid SnapSourceSettings.

Snapping can be used during interactive edits that move existing vertices using the VertexTool. It is also supported for adding new vertices for input devices with a hover event (such as a mouse move without a mouse button press).


Using the magnifier with a vertex move allows users of touch devices to clearly see the visual cues for snapping.


The snapping functionality provides one of a series of geometry editing enhancements that will roll out in future releases.

Attribute editing with feature forms

New to Native Maps SDKs in 200.4 is support for attribute editing using feature forms. Feature forms streamline the attribute editing experience across the ArcGIS ecosystem and are now supported in the .NET Maps SDK, Kotlin Maps SDK, and Swift Maps SDK. For more information about using the feature forms API, see the Edit attribute values topic in this guide.

A new toolkit component provides an out-of-the-box feature forms editing experience that you can integrate into your apps. For more information about the toolkit capabilities, see the FeatureFormView component in the .NET Toolkit.

The toolkit component provides a convenient way to add attribute editing capabilities to an app without writing a lot of code. It supports a variety of control types for accepting input attribute values, including single-line and multi-line text boxes, multiple choice controls (such as combo boxes and radio buttons), on/off switches, and a date-time picker control. These editing controls can be arranged and organized into groups and support custom Arcade expressions to control whether form controls are visible, editable, or require a value. Arcade expressions can also be used to compute the value for an attribute (perhaps based on the value of other attributes).

Editing with a FeatureForm

If you need a more tailored attribute editing UI and user experience, use the API to read the form definition from a feature layer in a web map and build a completely custom UI that fits your requirements. See the FeatureForm class for more information.

The following feature form functionality isn't currently supported: Editing the subtype field, attachments, relationships, and barcode input type.

Layers and display

Support for OGC 3D Tiles Layer

This release of ArcGIS Maps SDKs for Native Apps adds support for a new layer type Ogc3dTilesLayer. The layer is based on the OGC specification for 3D Tiles. With Ogc3dTilesLayer, you can add 3D Tiles data from a public service, portal item, or a local file that includes .3tz files. The layer behaves similar to ArcGISSceneLayer and can also participate in 3D analyses.

Clustering support for GraphicsOverlay

This release adds support for clustering point graphics on a GraphicsOverlay in dynamic rendering mode. In addition, there are new APIs to highlight an aggregate geoelement in a clustered FeatureLayer or GraphicsOverlay and get access to the underlying geoelements.

Dynamic entity track line rendering

With this release, track line attributes have been enhanced to include the entity ID attribute that uniquely identifies the track. This means you can now apply a renderer to TrackLineRenderer in the TrackDisplayProperties that highlights or distinguishes between tracks using one of the attribute-based renderers.

Data and query

New field types

ArcGIS Maps SDKs for Native Apps now supports fields to store the following types of date and time values:

  • Date only—Store values that indicate a day, month, and year. No time values are stored for date only fields.
  • Time only—Store values that describe a moment in time (hours, minutes, and seconds).
  • Timestamp offset—Store date and time values that include the time offset from the Coordinated Universal Time (UTC).

Big integer and 64-bit ObjectID fields are also now supported.

Relative date and time queries

Relative date and time queries are now supported with all date fields (except time only) by providing the intervals in the query. Relative date queries can be performed relative to the current date or to a specified (anchored) date.

Utility networks

Support for shortest path traces while offline

ArcGIS Maps SDKs for Native Apps now supports the shortest path trace type for offline utility networks. This type of trace requires two starting points and a network attribute (such as shape length) and returns the shortest path based on the provided attribute. This means that utility networks with full topology from a stand-alone or sync enabled mobile geodatabase now support all of the trace types that utility networks from a feature service support.

Licensing changes

A Utility Network extension license is no longer required to analyze (trace) utility networks, and has been removed from these methods: UtilityNetwork.TraceAsync(), UtilityNetwork.QueryNamedTraceConfigurationsAsync(), and Map.GetNamedTraceConfigurationsFromUtilityNetworkAsync().

A new Advanced Editing extension license is now required to edit utility network features as well as create a version and edit features and tables in a branch version enabled feature service. This extension requires a minimum ArcGIS Runtime license level of Basic. Detailed information about the licensing changes made for ArcGIS Maps SDKs for Native Apps 200.4 and the specific methods that will require this license extension can be found in the License levels and capabilities topic in this guide.

Indoor positioning

Indoor positioning definition property on maps

An IndoorPositioningDefinition property is now exposed from the Map class. For an IPS-enabled map, it provides all information needed to create an IndoorsLocationDataSource and conforms to the ILoadable pattern.

New constructor for an indoors location data source

This release adds a new constructor to the IndoorsLocationDataSource that takes an IndoorPositioningDefinition. This provides a consistent and straightforward approach for creating an IndoorsLocationDataSource using IPS information stored with an IPS-enabled map.

Indoors location data source configuration

An IndoorsLocationDataSource can now be configured using an instance of the new IndoorsLocationDataSourceConfiguration class.


Support for Arcade 1.26

This SDK now supports Arcade 1.26

The following linear referencing functions have been added:

Notes: KnowledgeGraph functionality which is available in Arcade version 1.26 with support in Pro and Online will be available in a future ArcGIS Maps SDKs for Native Apps release. The profile variables, $userInput and $graph, added to the PopUp and Popup Element profiles are currently set to null. A non-null $userInput implementation is planned for an upcoming release.

Projection Engine updates

Coordinate systems and transformations

Available coordinate systems and transformations have been updated to EPSG v11.003. These include the Equi7 projected coordinate systems, which divide the world into seven continental areas and are designed for imagery use. New vertical transformations based on geoids, quasi-geoids, or other conversion grids can transform to or between gravity-related vertical coordinate systems for the British Isles, Corsica (France), Finland, New Zealand, St. Helena Island, and the United States. The National Geodetic Survey's historic geoid models (GEOID99, GEOID03, GEOID06, and GEOID09) and VERTCON 3.0 conversion grids for the United States are now supported. Vertical transformations using VERTCON 2.1 grids are deprecated but remain available. Transformations using VERTCON 2.1 grids appear at the bottom of the list of transformation paths.

SDK enhancements

S-63 encrypted ENC data support on all platforms

In addition to Windows, support for S-63 encrypted ENC data is now available on all platforms, including Android, iOS, Mac Catalyst, UWP, and Windows on ARM64.

Analyzer warning for missing NuGet packages

A new analyzer has been added to .NET MAUI nuget pacakges that throws a build error if UseArcGISRuntime() is missing from the app. Similarly, when using .NET Maps SDK Toolkit, a build error is thrown if UseArcGISToolkit() is missing.

Portal user properties

The following new properties are added to the PortalUser class: UserID, AvailableCredits, and Categories.

Improvements and optimizations

  • Added support for hosting .NET MAUI visuals in the Callout.
  • Added a new property ArcadeEvaluator.Profile to return the Arcade profile under which the Arcade script should evaluate.
  • Enhanced SystemLocationDataSource on iOS to allow background location updates to persist when the device screen is powered off and/or the app is in the background.
  • The .NET Maps SDK template for .NET MAUI now enables null annotations by default and more closely matches Microsoft's .NET MAUI templates.

Enhancements and new features for the .NET Toolkit

This release adds a new toolkit component FeatureFormView on WPF and .NET MAUI. The FeatureFormView control presents an attribute editing UI by reading a form definition stored with a web map.

Breaking API changes

There are no breaking changes with this release.

Behavior changes

  • ArcGIS Pro 3.3 introduces the ability to define output fields (Reverse Output Fields) for reverse geocode operations. With locators created using ArcGIS Pro 3.3 and later, only fields enabled in Reverse Output Fields are returned from a reverse geocode operation in 200.4 and later. Supported output fields for geocode operations (including reverse geocode) are listed in the REST API under Geocode Service output fields. For locators created before ArcGIS Pro 3.3, reverse geocode results contain all output fields. In a future release of ArcGIS Maps SDK for .NET, all locators will only be able to return supported output fields in reverse geocode results.

  • Following the deprecation of VERTCON 2.1 and introduction of VERTCON 3.0 by National Geodetic Survey, vertical transformations using VERTCON 3.0 grids will now be returned from appropriate TransformationCatalog calls. Vertical transformations using VERTCON 2.1 grids remain usable and will still be returned from TransformationCatalog.GetTransformationsBySuitability calls but will now appear at the bottom of the returned lists which are sorted by suitability. To make use of transformations using VERTCON 3.0 grids, the required grid files must be deployed with your app. These can be found in the Projection Engine Data download for this release. See the Projection Engine updates section for additional coordinate system and transformation enhancements introduced with this release.

  • A new date-handling mode has been added to the .NET Maps SDK, configurable via ArcGISRuntimeEnvironment.EnableTimestampOffsetSupport. Previously, attributes of type Date accepted either DateTime or DateTimeOffset values. ArcGIS platform introduced new datetime field types. To prevent ambiguity with TimestampOffset field type, Date fields now exclusively use DateTime values. Additionally, domains and renderers for Date fields switch from DateTimeOffset to DateTime in this mode. This new behavior is currently opt-in but is necessary for compatibility with TimestampOffset fields.


API deprecations

There are no API deprecations with this release.

OS and framework deprecations

  • Support for iOS/iPadOS 15 is deprecated. The last release to support this version is 200.4. A minimum of iOS/iPadOS 16 will be required at the next release.
  • Support for macOS Monterey (version 12) is deprecated. The last release to support this version 200.4. A minimum of macOS Ventura (version 13) will be required at the next release.

Issues resolved

Issues addressed in this release are listed below.

  • Question on Esri Community: MapView not responding to touch pan input on WPF.
  • Authentication workflow fails to detect certificate requirement on encountering TLS handshake failure.
  • Authentication fails with ArcGIS Enterprise deployments that use non-default port numbers.
  • Unhandled exception when using keyboard to zoom on Windows.

Known issues

Known issues or limitations for this release are listed below.

  • BUG-000166643: A sceneview containing a scene with vector tiled layer can result in a crash if it's created and destroyed repeatedly. A possible workaround is to avoid using a vector tiled layer as a basemap, for example as an imagery basemap.

Changes in samples

New samples


  • Sample viewer
    • Updated .NET MAUI sample viewer to use .NET MAUI 8.0.6 packages.
    • Added links to sample GitHub folders from each sample.
    • Added functionality to create bug reports and feature requests on GitHub through sample viewers.
    • Added button to copy all file content to sample source code tab.
    • Improved appearance of .NET MAUI categories flyout and sample search.

Bug fixes

  • Replaced the sliders with pickers in the Configure clusters sample to prevent cluster flickering.
  • Improved .NET MAUI sample viewer performance when switching categories.
  • Fixed issue preventing samples being opened through search results on .NET MAUI iOS and MacCatalyst.

Your browser is no longer supported. Please upgrade your browser for the best experience. See our browser deprecation post for more details.