In September we released ArcGIS Runtime Local Server SDK 100.9. This incremental update maintained the support for map and geoprocessing packages created with ArcMap at 10.8.x and incremented the support for packages created with ArcGIS Pro to 2.6.
We are pleased to announce the 100.9 release of ArcGIS Runtime SDK for .NET. This release includes significant new features, enhancements to existing features, performance improvements, and bug fixes. You can read about the highlights common to all ArcGIS Runtime SDKs in the shared ArcGIS Runtime blog post and additional details in the 100.9 Release Notes. For you - our .NET community - here are several more details we would like to highlight.
We are proud to announce the release of 100.9 of ArcGIS Runtime SDK for Qt. This release brings to life all of the latest and greatest Runtime functionality mentioned in this blog, along with some notable changes specific to the Qt SDK as well.
If you are using ArcGIS Runtime SDK for Qt and you require support for Integrated Windows Authentication (IWA), you must use version 5.12.x or 5.13.x for the time being. Qt 5.14 introduced a bug in Qt's networking stack which will prevent you from successfully issuing IWA network requests. This means that workflows such as signing into your organization and accessing your secured maps and layers will not work. This bug is present in 5.15.0 as well. Once the mentioned bug is resolved, ArcGIS Runtime SDK for Qt should begin working as expected with the patched version of Qt. Please reach out to the team on GeoNet if you have any questions.
If you are using any static method from the Runtime QML API (e.g., ArcGISRuntimeEnvironment.createObject(), SpatialReference.createWgs84(), GeometryEngine.project(), etc.), with version 100.8 or older, those methods will not work with Qt 5.15. The most reliable solution in this case is to use an older version of Qt, such as 5.12, 5.13, or 5.14. For upcoming releases of the software (version 100.9 and beyond), the majority of cases will begin to work again with no code changes, and a handful of cases will require a minor code change (see below). This issue does not affect the C++ API.