Release Notes
Version 0.60.1 - 03/09/2024
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 ReferenceMap
New features
- Introduce a different style for the destination marker and waypoints that are outside of a reachable driving range.
Updates
-
The following are now available in Public Preview:
TomTomSDKMapDisplay.Route.areInstructionsVisibleTomTomSDKMapDisplay.RouteOptions.areInstructionsVisible
Fixes
- Change the fetch-style scheduler to a background process that will not hang the main queue when reading style from the cache.
- Fix the missing transition to navigating camera when starting navigating.
Navigation
Updates
-
The following are now available in Public Preview:
TomTomSDKNavigationTileStore.CachingConfiguration.init()TomTomSDKNavigationTileStore.CachingConfiguration.init(storageConfiguration:maxMemorySize:)TomTomSDKNavigationTileStore.CachingConfiguration.storageConfiguration
Fixes
- Previously,
DeviationEventwas not sendingtypeAndConfidence. This issue is now corrected. - Previously, all lanes were recommended in lane guidance. This issue is now corrected.
- Previously, the navigation instruction panel would freeze after route deviation. This issue is now corrected.
Personalization
Breaking changes
TomTomSDKPersonalDataDefault.PersonalDataFactory.create(with:)andTomTomSDKPersonalDataDefault.PersonalDataFactory.create()provide theTomTomSDKPersonalData.PersonalDatainstance with Core Data storage; previous JSON-based storage is ignored. To use a new storage mechanism use the new file path name or remove previous storage file.
Routing
New features
- Enable specifying manual charging stops for the Orbis map.
Search
Breaking changes
- Remove
roadUsesparameter fromTomTomSDKReverseGeocoder.ReverseGeocoderOptions.init(position:heading:radius:locale:roadUses:areaTypes:preferClosestAccurateAddress:fetchGeometry:)Public Preview initializer. We don’t recommend usingroadUseswhen constructing reverse geocoding requests.
Updates
- Add
TomTomSDKReverseGeocoder.PlaceMatch.init(place:navigablePosition:matchType:geometry:routeNumbers:speedLimit:boundingBox:)as Public Preview.