Release notes for 100.14

This page provides details about enhancements in the 100.14 release of ArcGIS Runtime API for iOS. It also lists deprecations, resolved issues, and known issues.


Issues Resolved

BUG-000149131 A Vector Tile Package (VTPK) that can be opened in ArcGIS Runtime SDK for .NET 100.12 returns errors when opened in ArcGIS Runtime SDK for .NET 100.13 and ArcGIS Runtime SDK for .NET 100.14.

BUG-000149413 Crash when calling Popup.FromGeoElement(geoElement) for KML Placemarks.

BUG-000149419 popupManager.finishEditing triggers arcade expression is invalid error from featureTable.add(feature).

BUG-000149423 Locators created with ArcGIS Pro 3.0 fail to load in runtime with error "Geocoder creation error: file too small to contain valid file header".

BUG-000149646 Geotriggers do not create fences for all features from a paged Service Feature Table.

BUG-000149734 Feature layer rendered beneath basemap contents.

BUG-000149750 Include the attribute rule name in the evaluation error message.




Evaluate Arcade expressions

Runtime now supports incorporating AGSArcadeExpression into your applications. You can create an AGSArcadeEvaluator to evaluate an Arcade expression under a given AGSArcadeProfile. You can query the Arcade evaluator to get the list of supported profile variables for a given feature table or geoelement. The profile variables can then be used to evaluate the script using AGSArcadeEvaluator.evaluateWithProfileVariables:.

For more general information on the Arcade scripting language and its uses, refer to the Arcade online documentation.

Arcade console function support

ArcGIS Runtime now supports capturing and logging Arcade script debug messages generated by the Arcade Console() function. You can do so by subscribing to the AGSArcGISRuntimeEnvironment.arcadeConsoleMessageHandler callback event. This can be useful when debugging Arcade scripts used in attribute rules, labeling and popups.

Maps and layers

Define custom map extent

You can now define an extent that restricts the map area accessible to the user. Until 100.14, the available area has been defined by the full extent of the basemap or the first operational layer if a basemap isn't provided. With this release, you can set a maximum extent with the new AGSMap.maxExtent property to restrict the extent to a focused area. Defining a restricted maximum extent may be useful if you are using a basemap that covers the entire world but your app is only designed to be used within a certain region.

Generate image service legend

ArcGIS Runtime now supports generating a legend for raster layers that are based on ArcGIS Image services. The legend can be accessed using AGSLayerContent.fetchLegendInfosWithCompletion:, which is implemented by many layers including the raster layer. The Legend Toolkit component uses this mechanism to now include legends from raster layers based on Image services.

Create feature layers from portal Items

ArcGIS Runtime now adds an AGSFeatureLayer constructor that takes an AGSPortalItem. This constructor accepts portal items that reference FeatureServer and MapServer URLs that include a layer ID.

Support multiple popup elements

At 100.14, the API has been enhanced to support multiple popup elements in an AGSPopup. Popup elements provide a richer experience by allowing you to mix and match different content types such as media, fields lists and text in a single popup. You can author maps and scenes containing these types of popups using ArcGIS Pro or the Map Viewer and Scene Viewer web apps. You can also define these popups in code using AGSPopupDefinition. AGSPopupManager.evaluatedElements allows you to access the popup elements so that you can display them in your custom UI. The AGSPopupsViewController UI component will be enhanced at a future release to display all popup elements in a popup.

Offline maps

Cancel server-side jobs

This release makes it easier to manage long running, server-side jobs. The new AGSJob.cancelWithCompletion:() method sends a request to cancel jobs running on the server (for example, exporting tiles or creating geodatabases) and lets you know when the cancellation has completed. This is crucial for reducing the overhead of redundant jobs running on the back-end, particularly in environments with several users creating jobs.

Add KVO support for Job properties

KVO support has been added to two AGSJob properties. KVO on AGSJob.status notifies you that a job has changed status (for example moving to the succeeded status), and KVO on AGSJob.Messages notifies you that a new message has been logged for the job.

Export Esri elevation data

You can now export elevation data as offline tile packages (.tpk or .tpkx) from Esri's elevation services, such as Terrain 3D or Bathymetry. You can use these elevation tile packages to construct offline scenes, as well as to perform 3D analysis, like viewshed or line-of-sight.

Download scheduled updates and upload new features

A new, optimized workflow improves offline data collection. Building upon the existing read-only scheduled updates workflow, you can now take a map offline so that it:

  • Receives regular update packages directly from the map area, without placing load on feature services.
  • Allows new features to be created on the client and uploaded directly to feature services.

The new AGSPreplannedUpdateMode value of AGSDownloadScheduledUpdatesAndUploadNewFeatures is part of the preplanned workflow and is highly scalable for scenarios where a large number of field workers need to be able to efficiently update their offline maps while still collecting data. This workflow only supports adding new features and does not include editing or deleting existing features.

Device Location

Read Geotriggers from maps

ArcGIS Runtime now supports reading geotriggers (AGSGeotrigger) directly from a web map or mobile map package. This enables your app to monitor new geotrigger conditions defined by the map author without writing custom code. The ability to author maps that include geotriggers will be available in other Esri products soon. Geotriggers from a map can also advertise a list of requested actions, such as showing pop-ups or enabling editing or tracking. Your app can use these requested actions to select geotriggers that match supported functionality.

New location data source status value

The AGSLocationDataSourceStatus enum has been enhanced with a new value: AGSLocationDataSourceStatusStopping.

Location data source error details

KVO support has been added for the AGSLocationDataSource.error property to provide error details when an AGSLocationDataSource is unable to start.

Indoor positioning system (IPS)

Caching of pathways

AGSIndoorsLocationDataSource now supports caching of the pathways table for use offline. Caching this data also reduces memory usage, especially when an indoor map contains many floors and pathways.

Apple Indoor Maps and Positioning

Indoor positions on an iOS device can be interpolated using Apple indoors positioning.

Improved positioning accuracy

Overall positioning accuracy in this release has improved for all usage scenarios: BLE, Wi-Fi, GNSS, and Apple. Note that full support for Wi-Fi based positioning will be available with ArcGIS Pro 3.0.

Indoor location data source warnings

ArcGIS Runtime 100.14 adds a property, AGSIndoorsLocationDataSource.warning (with KVO support), to provide notifications about potential problems with IPS positioning. Such warnings are not fatal but can influence the accuracy of final position estimation. For example, a warning like Pathways table cannot be loaded means locations won't be snapped to the predefined indoor paths, which may result in a less accurate position displayed for the user.

Scenes (3D)

Control labeling of point scene layers

Labeling is now supported on AGSArcGISSceneLayer when the source is a point scene layer. A new property, AGSArcGISSceneLayer.labelsEnabled, controls the display of labels for the entire layer. Labeling of ArcGIS scene layers is currently only available when the source is a point scene layer, and the property has no effect on other scene layer source types that you also work with via the ArcGIS scene layer (3D Object scene layer and integrated mesh scene layer).

Reprojection of 3D object and integrated mesh scene layers

The AGSArcGISSceneLayer and AGSIntegratedMeshLayer classes now support on-the-fly reprojection from the coordinate system in which they were published to the coordinate system of the scene, which is WGS84. Due to the computational cost associated with reprojecting data, it's recommended to store all data and layers in the same spatial reference as your basemap.

Indexed 3D scene layer (I3S) v1.7 Draco geometry support

ArcGIS Runtime now supports the Draco open source library for compressing 3D geometries in 3D object scene layers (AGSArcGISSceneLayer) and Integrated Mesh Scene Layers (AGSIntegratedMeshLayer). Publishing scene services and scene layer packages with Draco geometry compression results in significantly smaller nodes within the layer cache. Depending on the size, complexity, and i3S version of your data, you may see rendering time reduced by up to 30%, memory usage reduced by up to 20%, and reduced network traffic and disk I/O, resulting in a more responsive user experience.

To ensure that you can take advantage of the latest improvements with your data, use the I3S converter in the I3S GitHub repository to update the version of an integrated mesh or scene layer package (.slpk) to the latest version. You can also use ArcGIS Pro's Create 3D Object Scene Layer Package and Create Integrated Mesh Scene Layer Package geoprocessing tools to create scene layers at the latest version.

Improved scene view rendering

Improvements have been made to how ArcGIS Runtime calculates which tiles are required to render a current scene view. These improvements can result in a 30-40% reduction in the number of tiles that are requested for all raster and vector tile layers when rendering a scene view, reducing rendering times.

Geometry and spatial reference

Geodetic implementation of nearest coordinate

A new method in this release, AGSGeometryEngine.geodeticNearestCoordinateInGeometry, provides an alternative to the existing nearest coordinate method (planar). This new method uses a shape-preserving geodesic approximation of the input geometry to perform the calculation.

Vertical units of distance

A new property, AGSSpatialReference.verticalUnit, allows you to get the vertical units of distance for any spatial reference that has a vertical coordinate system.

Additional vertical transformations

Vertical transformations have been added for Estonia, Latvia, Lithuania, Switzerland, and Tasmania.


Create mobile geodatabases

This release introduces the ability to create and modify mobile geodatabases. This includes the ability to create and edit feature tables within a mobile geodatabase. Mobile geodatabases created with ArcGIS Runtime behave like mobile geodatabases from any other source. See the Work with data files topic for more information.

Read domains in geodatabases

ArcGIS Runtime now provides the ability to read a list of domains in mobile geodatabases and service geodatabase replicas.

Support for attribute rules

This release introduces attribute rules to help improve data integrity and editing efficiency. Two kinds of attribute rules are supported:

  • Constraint rules uphold data quality and prevent invalid data entry by ensuring that user-defined requirements are met.
  • Immediate calculation rules increase editing efficiency by automatically populating attributes or by making related edits to other geodatabase objects.

Attribute rules are written using the Arcade scripting language and configured on geodatabases using ArcGIS Pro. See the Introduction to attributes rules topic in the ArcGIS Pro documentation for general information about attribute rules.

Attribute rules are supported as follows:

  • When using a feature service or a stand-alone mobile geodatabase with attribute rules defined, ArcGIS Runtime will execute constraint and immediate calculation rules at edit time.
  • When using a feature service, rules defined with the Exclude from application evaluation tag will not be executed on the client, but instead will run on the server when AGSServiceGeodatabase.applyEditsWithCompletion: is called. Edits made by the server due to rule execution are automatically reflected in your ArcGIS Runtime app.

Support contingent values in PopupManager

AGSPopupManager now provides support for validating contingent values and determining if a popup field belongs to a contingent values field group.


Access annotations and dimensions referenced from web maps

ArcGIS Runtime 100.14 can render AGSAnnotationLayer and AGSDimensionLayer published from ArcGIS Pro 3.0 and referenced from web maps. The annotation and dimension layers referenced from the web map must be separate services on an Enterprise server with version 11.0 or higher. If the web map is published to contain all its data, the server will intervene and the annotation or dimension layers will only appear as image layers rendered by the server.

Honor annotation and dimension layer barrier weight

ArcGIS Pro 3.0 exports the BarrierWeight of annotation and dimension layers. This is used by ArcGIS Runtime to determine how much of an obstacle to labeling the annotation or dimension weights should be. This property is accessible via the ArcGIS Runtime API as AGSAnnotationLayer.barrierWeight or AGSDimensionLayer.barrierWeight.

Network analysis

Improved performance

General performance improvements were made in network analysis that reduces solving completion times, especially for local service areas and routing.


The ArcGIS Runtime SDK for iOS Toolkit is an open source project with controls and utilities to help simplify some common development tasks. Visit the GitHub repo for more information and a list of available components.

Enhancements for this release include:

  • New component: FloorFilter. Shows sites and facilities, and enables toggling the visibility of levels on floor-aware maps and scenes.

Breaking API changes

There are no breaking changes with this release.

Behavior changes


Improved placement for straight oriented 2D polyline labels

In previous releases, the AGSLabelDefinition.textLayout property for 2D line labels placed labels at incorrect locations when AGSLabelTextLayout value was Straight and AGSLabelingPlacement was not an ...Along value. This has now been corrected such that the AGSLabelingPlacement for straight 2D line labels conforms to the enums of PointAboveRight for point features, PolygonAlwaysHorizontal for polygon features, and LineAboveAlong for line features.

Impact of parent layer's visibility in labels of statically rendered 3D feature layers

Previously, the features of a static 3D feature layer which were owned as part of a group layer would turn invisible when their parent layer dictated it, but the labels would remain. Now, the labels and features for these layers keep their visibility in sync in response to changes in parent visibility.

Point scene layers honor their initial labels enabled state

Previously, point scene layers would have labels enabled by default due to absence of an API to allow users to alternate between the enabled/disabled states. With the introduction of AGSArcGISSceneLayer.labelsEnabled in this release, this property is used as originally authored.


API deprecations

  • The BasemapType enumeration is deprecated. Many of the basemaps referenced by this enumeration are in Mature Support and will no longer be updated. You can instead use the geographically load-balanced services provided by the AGSBasemapStyle enumeration. These services also allow developers to monitor usage with API keys and named users. The basemap helpers on Basemap have also been deprecated as they reference the same services. Use AGSBasemapStyle instead. To learn the life cycle plans of Esri basemaps, see Lifecycle for Esri's hosted raster basemap services. To learn the current lifecycle of all Esri’s basemaps, see Basemaps Life Cycle Support Status.

  • LocationDataSource.isStarted() has been deprecated in favor of AGSLocationDataSource.status.

  • The AGSServiceCurveGeometryMode value AGSServiceCurveGeometryModeFetchCurves is deprecated. This value will not be supported for future offline workflows with true curves and will be removed in a future release. If true curves are required in your online feature layer workflows, you should use the AGSServiceCurveGeometryModeTrueCurveClient mode and ensure that true curves are preserved correctly in any editing your app performs. If true curves are not required, then use the AGSServiceCurveGeometryModeDensifyCurves mode instead.

OS and framework deprecations

  • Support for iOS 13 is deprecated. A minimum of iOS 14 will be required at the next release.

To learn more about the future of ArcGIS Runtime SDK for iOS, see ArcGIS Runtime in 2022 and beyond blog.

Issues resolved

Issues addressed in this release are listed below.

BUG-000114058 Zooming in on an area that crosses the International Date Line results in the entire basemap.

BUG-000141154 Web Map Service (WMS) which ends with a slash, '/', fails to load and returns "Invalid XML" or "Layer failed to load" error messages.

BUG-000144236 The sublayer labels of a group layer are visible despite the layers being toggled off for the published line and polygon data on ArcGIS Online.

BUG-000145005 The maxFeatures property of AGSQueryParameters is zero by default.

BUG-000145979 Continuously increasing memory use when updating a graphic with new AGSPictureMarkerSymbol.

BUG-000146369 Graphic disappears from the map while switching between the two MapViews.

BUG-000146375 await table.LoadAsync() causes some Utility Network data to not display in the map view.

BUG-000146427 Continuously adding and removing group layers from map's operational layers increases memory.

ENH-000139990 Request for AGSGeometryEngine.geodeticNearestCoordinateInGeometry method.

Question on Esri Community ArcGIS Runtime is only requesting the 0,0 tile for a WMTS service with TileMatrixSetLimits.

Libtiff fixes

ArcGIS Runtime 100.14 includes Libtiff 4.2.0 with the following cherry-picked fixes applied in order to address specific security vulnerabilities. Note that scanning tools will still report Libtiff 4.2.0.

Known issues

Known issues or limitations for this release are listed below.

  • BUG-000149978 Add/update/delete feature operations that trigger attribute rules whose Arcade expression uses the Domain function will fail to evaluate in Runtime with an "Arcade expression is invalid" error message.

Changes in samples

New samples


Bug fixes

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