Release notes for 100.15

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


Issues Resolved

  • BUG-000157449 Application crashes intermittently when an offline map including a basemap and 10 operational feature layers with refreshInterval is loaded.

  • BUG-000148794 Several features fail to render despite zooming in and panning when featureRequestMode is onInteractionCache and tilingMode is disabled.

  • BUG-000155484 SubtypeFeatureLayer pointing to service with labeling info fails to load.

  • BUG-000153386 Reference scale not honored for some symbols in a SubtypeFeatureLayer.

  • BUG-000156196 PictureMarkerSymbol causes a memory leak when a new instance is created outside of the map view.

  • BUG-000157983 Reduce CPU usage when SceneView idles.

  • Using service-level applyEdits() fails to delete features in some cases.

  • System tables in a service are not correctly identified.

  • System table edits are not sent with calls to ServiceGeodatabase.applyEditsAsync().
  • Magnifier image is distorted after MapView is resized.
  • PopUp elements fail to create from returned Arcade dictionary.

  • Upgrade Protobuf 3rd-party library to 3.21.12 to avoid security vulnerabilities.

  • Portal fails to load after app restart when an invalid SecIdentityRef-based credential is provided.


Issues Resolved

  • BUG-000119969 Process memory leaks when adding and removing feature collection layers frequently.

  • BUG-000150574 Marker symbol rotation in feature collection not honored from webmaps.

  • BUG-000151826 Arcade expression shows inconsistent behavior in case sensitivity when Simple renderer and Dictionary renderer is used.

  • BUG-000152564 createTableAsync method of geodatabase ignores the vertical coordinate system of the table description.

  • The results of Arcade expressions are incorrectly cached between features in Media popup elements.

  • Distinguish between null being returned from an immediate calculation attribute rule and an empty return value.

  • Updating LabelDef.Symbol.Color after changing LabelDefinition does not work on specific layers.

  • Map does not refresh after setting a feature layer's definition expression to "field_name is null" when tiling mode is disabled.

  • Projecting curved feature geometry from Web Mercator to WGS 84 causes a crash.

  • Location updates for floor-aware geotriggers do not work with all integer types used to represent floor information.

  • Updated RouteTrackerLocationDataSource to support asynchronous start and stop methods to be consistent with those used by IndoorsLocationDataSource.

  • Modified the timestamp calculation used by the Kalman filter in the positioning estimation of IndoorsLocationDataSource, improving its accuracy.

  • Fixed a buffer underflow bug in the floor estimator that caused occasional crashes in IndoorsLocationDataSource.

  • Unable to delete features from hosted feature layers that do not have GlobalIDs.

  • Contingent values validation logic doesn't match ArcGIS Pro if there are no contingencies defined for the current subtype.

  • A UtilityNetwork created with a URL not matching the case 'FeatureServer' fails to trace, get associations with extent, and query trace configs.

  • A direction maneuver is sometimes missing from the results when a route traverses a feature with a self-intersecting geometry.

  • Upgraded zlib library to 1.2.13 to address security vulnerability.

  • Upgraded Libtiff from 4.4.0 to 4.5.0 to address security vulnerabilities.

  • Upgrade sqlite to version 3.39.2 to address vulnerability.




Line labeling improvements

At this release, labels on line features are kept in the visible extent when possible. This behavior is automatic (no additional API calls are required) unless repetition is being used along the line. If repetition is used then it is assumed that the author is deliberately controlling the approximate frequency of labels on the map in order to avoid clutter.

Line labels will also make more small local movements to avoid obstacle features or other labels. This applies to labels that use repetition and those that don't. For labels with repetition, this may affect the distance between repetitions.


Support for text symbol flip angle

ArcGIS Runtime now honors flip angle on a CIMTextSymbol. The flip angle property defines the angle at which rotated text is flipped (mirrored) in place. The property gets applied dynamically at rendering time and is not exposed via a public API. Angle is calculated in degrees from vertical. There are four different ways rotation can be applied to a symbol: map rotation, symbol rotation, geometry rotation, and marker rotation (defined on the respective symbol layer). Flip angle is not honored in 3D or if the text symbol's angle property is greater than 0.

Utility Network

Prevent subnetwork controller deletion

The utility network allows designating specific features as subnetwork controllers. Subnetwork controller features serve as network sources or sinks and form the starting points of a subnetwork. After a device or junction object has been assigned as a subnetwork controller, the feature cannot be deleted. Beginning with version 100.15, when attempting to delete a feature that is a subnetwork controller, ArcGIS Runtime will prevent its deletion.


Geotriggers are now floor-aware

Geotriggers that use floor-aware feature data can now make use of the level information provided by a floor-aware AGSLocationDataSource (such as the AGSIndoorsLocationDataSource) to limit notifications to fences on the correct floor. For example, notifications will only be sent when you enter/exit a fence based on a feature that is on the same floor as your current AGSLocation. If the location does not include floor information then the floor attribute of a fence is ignored.

Indoor positioning

Support for large positioning files

In previous releases, the AGSIndoorsLocationDataSource did not always work effectively on all platforms when using large positioning files (30 MB or more). With release 100.15, the indoor location data source can use positioning files up to 300 MB.

Improved indoor position accuracy

This release includes several improvements to indoor positioning system (IPS) accuracy.

  • Indoor positioning output that does not use path snapping is now more stable. The display presents fewer horizontal/sideways jumps and drifts and follows the user's actual position more precisely.
  • Positioning accuracy has been improved when the location data source switches between GNSS and IPS.
  • Floor level estimation is now more accurate.

Improved output

  • AGSIndoorsLocationDataSource will no longer send warnings that are not relevant to the diagnosis of indoor location data source issues.
  • The timestamps for indoor location data source positioning output are now correct for estimated positions. AGSIndoorsLocationDataSource will no longer output the last known position when a position cannot be estimated.


Arcade improvements

At this release, ArcGIS Runtime supports Arcade 1.19, which has the following enhancements.

  • Support for while loops like the one shown below.
Use dark colors for code blocksCopy
var count = 1
while (count < 10){
  count *= 2
  • Simplified Dictionary construction where the name of an entry is the same as the variable containing the value.
Use dark colors for code blocksCopy
var hello = "Hello"
var name = "Arcade"
{hello, name} // Equivalent to {"hello":hello, "name":name}
  • A new ConvexHull function added to the set of geometry functions.
  • The FeatureSet constructor can now accept a dictionary.

For more information, see the Arcade documentation.

Enhanced support for attribute rules

ArcGIS Runtime 100.15 adds support for the following Arcade data functions for use with attribute rules:

  • GetFeatureSetInfo() returns metadata for the original source database and service (if applicable) of a feature set. This function was added in Arcade version 1.18.

  • NextSequenceValue() returns the next sequence value from the database sequence specified. This function executes locally when called from attribute rules running in stand-alone mobile geodatabases.

Projection engine updates

The following changes have been made to coordinate systems, map projections, and geographic transformations:

  • Several planetary satellites and extraterrestrial bodies had updated definitions added based on the IAU/IAG 2015 publication. Projected coordinate systems for Mars and the moon were also added.

  • The Luxembourg 1930 name was updated to LUREF which affected geographic and projected coordinate systems and several transformations.

  • Several edits were made to geographic transformations:

    • The name of MGI_1901_To_WGS_1984_12, 8688, was updated to MGI_1901_To_WGS_1984_16.
    • The rotation values were fixed in 9383, KSA-GRF17_To_WGS_1984_1, and 9472, DGN95_to_SRGI2013_1.
    • The transformation method was fixed in 1825, Hong_Kong_1980_To_WGS_1984_1.
    • The WKIDs and transformation methods were updated for CR05_to_CR-SIRGAS_1 and CR05_To_WGS_1984_2.
    • A rotation value was fixed in 8827, Camacupa_2015_To_RSAO13_1.
  • Many years ago, the EPSG registry ( deleted entries that had problems. They added corrected entries with new well-known IDs (WKID). This included a large group of geographic transformations where the ‘old’ WKIDs were in the 8xxx range. Esri kept the previous WKIDs in case someone was using them, but ‘code-changed’ the objects to use the official WKIDs. EPSG has started reusing the 8xxx numbers, although only a few objects so far have been affected. The code-change entries that used 8xxx (and which no longer exist in the EPSG registry) were removed at this release. This allows us to use the 8xxx values for new EPSG entries. Five GDA2020 transformations were affected and had been given Esri WKID numbers (108xxx). They now have code-change entries to their official EPSG WKID numbers. These are:

    • GDA_1994_To_GDA2020_1, 108060 to 8048
    • GDA_1994_To_GDA2020_NTv2_2_Conformal_and_Distortion, 108447 to 8447
    • GDA_1994_To_GDA2020_NTv2_3_Conformal, 108446 to 8446
    • GDA_1994_To_GDA2020_NTv2_4_Christmas, 108444 to 8444
    • GDA_1994_To_GDA2020_NTv2_5_Cocos_Keeling, 108445 to 8445
  • Several new vertical transformations based on geoids, quasi-geoids, or other conversion grids are available. You can use them to transform to or between gravity-related vertical coordinate systems for the following areas: Belgium, Estonia (geoid file distributed by AlphaGIS, Estonian distributor), Italy (EVRF 2019), Latvia, Lithuania, Switzerland, Tasmania (Australia), Ukraine (EVRF 2019), and United Kingdom (HS2-VRF).

  • Projection mathematics for the Hotine oblique Mercator projection and the Rectified skew orthomorphic projection have been modified to fix an issue with ±90° azimuth cases. This is expected to cause about 4 cm offset in the center of the Swiss projected coordinate systems (affected WKIDs are: 2056, 21780, 21781 and 21782). The projection algorithm has been added as a new variant to the Hotine oblique Mercator projection.

Support for iOS 16

Shortly after iOS 16 was announced during Apple's WWDC conference in June 2022, testing began on the developer and public betas to ensure apps built with ArcGIS Runtime could adopt it quickly. Following the official release of iOS 16 on September 12, 2022, ArcGIS Runtime 100.15 was certified to support iOS 16.

Breaking API changes

There are no breaking changes with this release.

Behavior changes

  • Layers imported from ArcGIS Pro 3.0 that specify labels be offset to the Left or the Right of a line feature (following its digitization direction), will now have that positioning respected rather than defaulting to Above and Below the line feature on the screen.
  • Horizontal labels offset from a line feature are now positioned so that their closest point is at the expected offset from the line feature. This was not previously correct in all cases, especially when the map was rotated.
  • Labels are no longer lost when elevation changes.


API deprecations

There are no API deprecations with this release.

OS and framework deprecations

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.

  • Question on Esri Community WMTS layer fails to load with "Invalid argument: tile info origin must have a spatial reference"
  • Question on Esri Community Changing Opacity of a Surface without Basemap doesn't update on screen
  • BUG-000134159: Ordering fields by OrderByFields.Add(orderBy1) in a mobile map package (.mmpk) with 40,000 features fails with an error.
  • BUG-000148570: The 2D MapView flickers when displaying the mobile map package data using FeatureRenderingMode.Dynamic or FeatureRenderingMode.Automatic.
  • BUG-000149335: The zoom and pan tools built in ArcGIS Runtime SDK 100.14 result in white tiles.
  • BUG-000149425: Mobile geodatabase is returning a "No Data" error even though there is data in the mobile geodatabase.
  • BUG-000149646: Geotriggers do not create fences for all features from a paged Service Feature Table.
  • 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.
  • BUG-000148700: App crashes on real devices when loading a mobile map package (MMPK) file containing a layer nested in multiple group layers.

Known issues

There are no known issues or limitations for this release.

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.