Release Notes
Version 0.75.3 - 04/11/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 ReferenceLocation
Fixes
- Fix an occasional crash during navigation that happened when
TomTomSDKLocationProvider.DefaultCLLocationProvider.lastKnownLocationwas read while a new device location was being written to it.
Routing
Fixes
- Fix a crash in
TomTomSDKRoutePlannerOffline.OfflineRoutePlannerwhen planning or replanning a route from onboard map data produced a route the SDK couldn’t use.
Version 0.75.2 - 22/10/2026
Navigation
Fixes
- Fix navigation planning a new route as if the vehicle had left the route, while the vehicle was still driving on it. This happened on routes longer than about 37 km with default settings:
TomTomSDKNavigation.NavigationActiveRouteChangeObserver.didChangeActiveRoute(route:)reported a new active route, and drivers could hear a route recalculation. - Fix
TomTomSDKNavigationEngines.LocationContextreporting an outdated speed, street name and speed limit while driving.TomTomSDKNavigationEngines.LocationContext.speednow follows the current map-matched speed on every update. When the SDK stops receiving road data around the vehicle, the street name andTomTomSDKNavigationEngines.LocationContext.speedLimitare no longer kept indefinitely: after 3 seconds without road data they are reported as unknown until the data is available again.
Version 0.75.1 - 15/10/2026
Navigation
Fixes
- Fix the speed limit dropping out while the vehicle is stopped or moving slowly with an unstable GPS signal. The SDK no longer publishes an off-road position when no GPS fix is available and the position cannot be estimated.
Telemetry
Fixes
- Fix a crash that could occur when the device had no network access for a long period of time.
Virtual Horizon
Fixes
- Fix no speed limit being reported on roundabouts and other traffic circles of NDS maps whose map data has no speed limit. The SDK now reports an estimated limit there: the lower of the entry and exit road limits, capped at 40 km/h in urban and 60 km/h in non-urban areas.
Version 0.75.0 - 21/09/2026
General
New features
- Add the Initialization Surface v1.0, a unified entry point for configuring and starting the SDK.
Common
Fixes
- Fix occasional app hangs that the SDK could trigger under heavy load through its internal logging. Log message values are now evaluated lazily, only when they pass the configured log level.
Location
Fixes
TomTomSDKLocationProvider.DefaultCLLocationProvider.enable()no longer blocks the calling thread. Previously it could block while waiting for the last known location from the system location service, which could make the app briefly unresponsive.
Map Visualization
Updates
- The default 3D driving camera now uses the wider, less inclined configuration (tilt 20 degrees, field of view 35 degrees) during turn-by-turn navigation and free driving, giving drivers a broader view of the road ahead.
Fixes
- Traffic incident delays rendered on the route are now consistent with the delays shown in the ETA panel and in route planning. Previously the same incident could show a different delay in each place.
- Apply custom location indicator on main thread in
setCachedStyle. - Traffic flow is no longer displayed on the map when traffic has been disabled in settings and a cached map style is used.
- Fix an intermittent crash caused by a data race on the map display API key when it was read and written from different threads at the same time.
- 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.
- Show VehicleRestrictions for Trucks without load types.
Navigation
Fixes
- Announce simple lane guidance at distance 1.5 km.
- Fix
TomTomSDKNavigationEngines.LocationContext.speedreturning zero inside tunnels when dead reckoning is active. It now returns the estimated speed from the dead reckoning provider. - The speed limit no longer disappears during guided drive when the device stays stationary for 10 seconds or more, for example when waiting at a traffic light. Free drive was not affected.
- Voice instructions from the previous route are no longer played after a route deviation. Previously they could be repeated, which was confusing during navigation.
- Fix false route deviation that could occur near the route end when GPS degrades in a tunnel during an NDS.Live map tile rebuild.
- Fix advance guidance progress replanning triggering false route deviation events (
TomTomSDKNavigation.RouteAddedReason.deviated) even when the vehicle remained on the correct route. Navigation no longer incorrectly reports off-route during guidance increment replans. - 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 the raw location until map matching recovers, so the marker keeps moving.
Routing
Fixes
- Route arrival and departure times, along with their time zones, are now consistent across online and offline planners. Previously they could be off by hours in cross-timezone routes.
Deprecations
- Deprecate
minDeviationDistancein favor ofminDeviationTime.
Search
Fixes
- The SDK no longer crashes when parsing opening hours time ranges during daylight saving time transitions.
Virtual Horizon
Fixes
- Show an estimated speed limit on roundabouts whose map data has no defined speed limit. Previously the speed limit could appear blank on most roundabouts, particularly where the connecting roads have different speed limits. 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.
- Keep horizon data, such as the current speed limit, updating after the route changes. Previously the data could stop refreshing after a route change and stay at its last value for the rest of the drive.