August 2026 Platform Release Notes

HERE SDK

Upcoming version 4.27.3.0_LTS

Release process change

The HERE SDK release cadence has changed to a structured monthly cycle, with 12 planned releases per year. These include:

• 6 minor releases

• 4 major releases

• 2 LTS (Long-Term Support) releases. Designated LTS releases serve as the supported production baseline for customers and receive support for six months from their release date or until the next LTS release.

Hotfixes will only be provided for supported LTS releases, and will be limited to critical issues. This process takes effect with 4.27.3.0_LTS, which is currently planned for release on September 2, 2026.

Version 4.27.2.0

Bug Fixes and Improvements

• Map view: Added TileKey.fromGeoCoordinates(coordinates: GeoCoordinates, storageLevel: Int32, tilingScheme: TilingScheme) factory method for creating TileKey objects containing specific geographic coordinates.

• Map view: Added support for rendering a MapMarker icon above overlapping marker icons while still allowing its text label to participate in collision detection and remain hidden. See MapMarker.iconOverlapAllowed for details. This setting has no effect when MapMarker.overlapAllowed is set to true.

• Offline search: Added support in OfflineSearchEngine.searchByText(), OfflineSearchEngine.searchByAddress(), and OfflineSearchEngine.suggestByText() to interpret digits-only queries as house numbers when the enhanced algorithm is enabled. Search results and suggestions now include nearby addresses with matching house numbers.

• Map data: Added MapDataLoaderErrorCode.mapUpdateInProgress. Public methods of map data loaders now return this error if called during a map update.

• Map data: Added SegmentDataLoaderOptions.loadPolyline. When set to true, segment geometry is loaded with segment data.

• Offline routing: Improved route selection to more effectively avoid small roads for trucks weighing more than 7.5 tons on newer map versions.

• Removed the beta label from WarnerEngine, CustomWarning, CustomWarningProvider, LaneDecreaseWarning, LaneDecreaseWarningOptions, TollBooth, TollCollectionMethod, TollStopWarningListener, Warning, WarningListener, WarningOptions, WarningStatus, WarningUpdate, and WarningsRegistry. These features are now considered stable, and any future changes will follow a strict deprecation process.

Version 4.27.1.0

Bug Fixes and Improvements

• Map view

  • Added MapScene.addMapPolylineLayer(name:layerPriority:), letting users create a named polyline layer at a specific render priority.

  • Added MapScene.addMapPolyline(_:layerName:) and MapScene.addMapPolylines(_:layerName:), letting users add polylines to a named layer.

  • Added MapScene.removeMapPolylineLayer(_:), letting users remove a named polyline layer and all polylines it contains.

  • Added MapContext.SceneLoadCacheOptions and MapContext.MemoryManagementOptions.sceneLoadCacheOptions for scene-load cache customization. Note that this feature is in beta.

  • Added support for POI filtering with MapContentSettings.configurePoiFilter(with:) and MapContentSettings.resetPoiFilters(), using the new types EVPoiFilterCriteriaBuilder, ElectricCurrentType, and ElectricVehicleType to create a PoiFilterCriteria. Note that this feature is in beta.

• Electronic horizon: Added weak-listener support for ElectronicHorizonEngine.addElectronicHorizonDelegate(_:).

• Navigation: Added VisualNavigator.routeLayerOverlay to expose the name of the internal route polyline placeholder layer. Pass this name to build MapLayerPriority and use MapScene.addMapPolylineLayer(name:layerPriority:) to position custom polylines above the navigation route. For custom polylines below the route, use the default map polyline layer. Note that this feature is in beta.

• Added support for distributing all-in-one bundles through an Artifactory Maven repository. The here-sdk-exploreand here-sdk-navigate bundles are now available through Gradle dependency resolution. Refer to the integration guide (https://docs.here.com/here-sdk/docs/android-integrate-here-sdk) for details. Note that this feature is in beta.

• Added support for modularization and for distributing required components through an Artifactory Maven repository. Refer to the integration guide (https://docs.here.com/here-sdk/docs/android-integrate-here-sdk) for details. Note that this feature is in beta.

The OCM base version was also adapted and now starts with OCM v.227 for RoW and 98 for Japan (MOM2-based).

HERE Real Time Traffic

• Coverage was expanded for the Predictive 3.4 protobuf feed, with tables added for SEA (Indonesia, Malaysia, Philippines, Singapore, Thailand, Vietnam, and Taiwan) and OCE (Australia and New Zealand) regions.

• Improvements to the 3.4 Flow Feed for deep coverage and stoplight changes in Australia.

• Improved Protobuf 3.4 rollout by increasing flow coverage for the UAE and Saudi Arabia regions.

• Traffic Incident Feed improvements for Malaysia.

• Traffic Incident Feed improvements for British Columbia.

• Traffic Incident Feed improvements for Pennsylvania.

• New source incidents were added to the Traffic Incident Feed for Kansas.

• Truck bias for Flow was reduced in Poland, Qatar, Romania, and Slovakia.

HERE EV Charge Points API

Deprecation Notice: EV Charge Points API v2

EV Charge Points API v2 is now deprecated. While it remains fully supported for existing customers, the API is now in the deprecation phase.

In its place, HERE recommends using:

• Geocoding and Search API v7 (GS7) with show=ev for EV charging station discovery and search.

• EV Charge Points API v3 for advanced EV charging content, including rich station attributes, tariffs, nearby places, truck-specific information, reliability data, availability predictions and busy times.

Note the following about EV Charge Points API v2:

• Existing customers will continue to receive the latest EV charging content updates.

• The API schema is frozen and will remain stable.

• No new features, enhancements, or attribute expansions will be added going forward.

For migration guidance, refer to the HERE EV Migration Guide - Introduction.

HERE Platform

Beginning October 1, 2026, API-based access to IAM organization or realm information will require explicit opt-in by the app manager. This will apply to all existing apps, as well as newly created apps. However, customers should not experience any impact on current app usage unless an app specifically depends on access to IAM organization or realm information.

This change supports HERE’s commitment to zero trust by ensuring that access is intentional, controlled, and aligned with least-privilege principles.

Frequently Asked Questions

• What is changing?

Starting , apps need app manager opt-in to access IAM org or realm information.

• Will my apps break?

No, not unless they specifically depend on IAM org or realm information.

• Who is responsible for making any necessary changes for access?

Only app managers for apps that need IAM org or realm information.

• What should I do?

If your app needs this access, follow the HERE documentation to opt in.

What’s changing

• API access to IAM org or realm information will require explicit opt-in by the app manager.

• This explicit opt-in requirement applies to all current apps and all newly created apps.

• Customers should not experience any impact on their current app usage unless an app or integration specifically depends on IAM org or realm information.

What’s not changing

General app functionality and other HERE APIs will continue to work as they do today. Apps that do not use IAM APIs or organization or realm information will not require any updates.

Who is impacted

This change affects only applications or integrations that directly call IAM endpoints or depend on access to information in IAM organizations or realms.

What you may need to do

No action is required unless your app or integration relies on information in IAM organizations or realms. If access is needed, the app manager must explicitly opt in. For instructions on how to opt in, refer to the HERE documentation.

Timeline

• Now through September 2026: Review whether any apps or integrations use IAM APIs or org or realm information.

• October 1, 2026: API access to IAM org or realm information requires explicit opt-in by the app manager.

How to get help

If you are unsure whether you are impacted or need help, contact HERE Support.

HERE Map Content v2

Removal of NameType values from the Name Model

The EXONYM and ADDITIONAL_EXONYM values in Name.NameType will be completely removed by the end of November 2026. Both values are already deprecated. A new exonym field has been added to the Name message structure and will be used instead.

Three new PayPoint types in the Toll Cost layer

To improve the representation of different toll-charging models, HMC introduces three new PayPoint types in the Toll Cost layer:

• CongestionZonePayPoint

• EnvironmentalZonePayPoint

• VignettePayPoint

These new types are available in the HMC schema starting in August 2026.

Schema changes

The TollSystem message has been extended with the following new PayPoint types:

CongestionZonePayPoint congestion_zone_pay_point = 6;
EnvironmentalZonePayPoint environmental_zone_paypoint = 7;
VignettePaypoint vignette_paypoint = 8;

The new PayPoint types behave similarly to TollSystemPayPoint, with costs associated with a toll system rather than a specific toll structure or entry/exit pair.

Important: Future content changes

Although schema support is being introduced in August 2026, HERE Map Content will not publish these new PayPoint types until January 2027.

By the end of January 2027, toll costs that are currently represented using TollSystemPayPoint may instead be represented as:

• CongestionZonePayPoint

• EnvironmentalZonePayPoint

• VignettePayPoint

This content migration may be a breaking change for consumers that explicitly depend on TollSystemPayPoint.

Consumers are encouraged to update their implementations during the transition period between July 2026 and January 2027 to ensure support for the new PayPoint types before content publication begins.

Removal of catalog history

The removal of catalog history has been postponed until the end of Q4 2026. An exact date will be communicated in a future Developer Note. Going forward, HERE will remove catalog versions older than 18 months.

For questions, contact your HERE Account Executive or Technical Services point of contact.

Restricted Driving Maneuver changes

In Q4 2026, a redesign of the Restricted Driving Maneuvers schema and implementation (Restricted Driving Manoeuvre) will be introduced.

This will impact the following layers:

• Topology Attributes (layer ID topology-attributes)

• Truck Attributes (layer ID truck-attributes)

Additional details will be announced later in Q3 2026.

Planned removal of layers

Following earlier messaging, by the end of Q3 2026, the following layers will be permanently removed from the HERE Map Content catalog:

• Pedestrian Attributes

• Bicycle Attributes

These products have been retired by HERE. For questions, contact your HERE Account Executive or Technical Services point of contact.

Removal of layers postponed

The removal of the Warning Locations (layer ID warning-locations) layer is postponed to 2027. This layer will be replaced by one or more new layers publishing an enhanced HERE Safety Cameras content offering.

The removal of the Vehicle Regulations (layer ID vehicle-regulations) and Commercial Vehicle Regulations (layer ID commercial-vehicle-regulations) layers is also postponed to 2027.

Both layers will be replaced by new layers that publish a new HERE Motorized Vehicle Regulations content offering. The new layers will be:

• Vehicle Regulations Attributes (layer ID vehicle-regulations-attributes)

• Commercial Vehicle Regulations Attributes (layer ID commercial-vehicle-regulations-attributes)

HERE Map Content v2 / HERE SDKs / Map Rendering Services

Coming Soon

Arabian Gulf Name Change

On , the default name for the Arabian Gulf will be changed to the Persian Gulf. This change also affects the default international map view used by HERE SDK Navigate and Explore, HERE Maps API for JavaScript, Vector Tile API, Raster Tile API, and Map Image API.

The Arabian Gulf name can be preserved by setting the politicalView parameter for any of the countries listed in the table below. For Türkiye, the politicalView parameter must be configured to retain the name Gulf of Basra. If the Arabian Gulf or Gulf of Basra name is desired, you must update your application logic accordingly.

All countries in the table below that did not already have a political view will have one added on or before . The three-month window between the creation of the political view and the default name change is intended to give customers sufficient time to implement the new view. During this period, implementing the view will have no impact on the naming of the Arabian Gulf.

These references explain how to set the political views for the affected countries:

• Android SDK

• Maps API for JavaScript

• Vector Tile API

• Raster Tile API

• Map Image Developer Guide