Release Notes
Version 0.74.0 - 11/08/2026
Discover the improvements and new features included in the following version.
Share your thoughts on this release by using the feedback button located at the bottom of the page.
For more in-depth documentation, check the API ReferenceGeneral
Fixes
- Fix black texture artifacts appearing on navigation instruction arrows on the map.
Common
Fixes
- Fix an issue where the app could appear frozen for 2 seconds or more (and risk being terminated by the OS) during navigation start-up.
Data Management
Fixes
- Restrict
TomTomSDKDataManagement.NavigationTileStoreto accept onlyhttp/httpsURLs, preventing invalid scheme configurations.
Map Visualization
Fixes
- Fix an app hang that could occur after onboarding, planning a route, or zooming the map.
- Fix a crash that could occur when adding or removing map markers.
- Fix an issue where after stopping navigation with a route, the location updates would jump back and forth.
- Fix a crash that occurred when tapping or panning the map far outside the visible globe.
- Fix a crash that could occur under certain timing conditions while the map view was being deallocated.
- Fix an oversized, incorrectly positioned location indicator (chevron) on CarPlay.
- Fix an
EXC_BREAKPOINT: isMainThreadcrash that occurred when the map was deallocated on a background thread while markers or other annotations were attached. Annotation cleanup during map deallocation is now performed on the main thread. - Fix a crash that could occur when rotating the device after navigation was canceled or no routes were present.
TomTomSDKMapDisplay.TomTomMap.hideTraffic()no longer stops working when the map re-applies its cached style, for example after changing the location indicator type. Previously the traffic flow layer became visible again and furtherhideTraffic()calls had no effect.
Navigation
Updates
- Rename Preventive to Continue Interim instruction.
Fixes
- Preserve the initially selected route during continuous replanning after a deviation, ensuring navigation consistency even if a more optimal route becomes available.
- The on-map location marker no longer freezes during navigation when map matching temporarily fails (for example in tunnels, or in areas with poor GPS or missing map data). The SDK now keeps reporting your raw location until map matching recovers, so the marker keeps moving.
Routing
Fixes
- Require valid
TomTomSDKRoutingCommon.RoutePlanningOptions.supportingPointsto be set whenTomTomSDKRoutingCommon.AlternativeRouteOptions.alternativeTypeisbetterRoute; omitting them now throws a validation error instead of sending a malformed request.
Search
Fixes
- Fix
TomTomSDKSearchOnlinefailing to display opening hours for fuel stations and parking POIs when the device uses a non-Gregorian calendar (Buddhist, Japanese Imperial, or Persian). Opening hours are now shown correctly regardless of the device locale and calendar system.
Virtual Horizon
Updates
- Add
TomTomSDKVehicleHorizon.PoiElementPublisherfor element typeTomTomSDKVehicleHorizon.PoiElement. - Add
TomTomSDKVehicleHorizon.SpeedLimitElementPublisherfor element typeTomTomSDKVehicleHorizon.SpeedLimitElement.
Fixes
- Fix a crash caused by certain map data configurations providing an invalid reference for a point of interest.
- Fix speed limits appearing blank on most roundabouts where the entry and exit roads have different limits; the SDK now shows an estimate.
- Prevent crash in Vehicle Horizon service.
- Show an estimated speed limit on roundabouts whose map data has no defined speed limit. Previously the speed limit could appear blank on such roundabouts. The estimate is the lower of the speed limits on the roads entering and leaving the roundabout, capped at a typical urban (40 km/h / 25 mph) or non-urban (60 km/h / 35 mph) maximum.
- The speed limit and road context no longer go blank when the horizon briefly resets or the position briefly leaves the mapped road during navigation. The last known values are kept for up to 3 seconds until the horizon recovers.