Release Notes

Fix a dex2oat verifier failure that occurred.

when integrating NavSDK into an Android Automotive (AAOS) system image. No action is required.

Logs no longer cut off if their size exceeds 4KB and are instead split into multiple lines.

OSE Automotive: Fix button issue when planning route.

The following APIs are now available in General Availability:

• method com.tomtom.sdk.datamanagement.nds.NdsStore.setUpdatesEnabled
• property com.tomtom.sdk.datamanagement.nds.NdsStore.updater
• method com.tomtom.sdk.datamanagement.nds.NdsStoreConfiguration.buildUpdateConfiguration
• method com.tomtom.sdk.datamanagement.nds.update.NdsStoreUpdateConfigurationFactories.kt.buildNdsStoreUpdateConfiguration
• property com.tomtom.sdk.datamanagement.nds.NdsStoreConfiguration.updateConfiguration
• class com.tomtom.sdk.datamanagement.nds.update.NdsStoreUpdateConfiguration
• secondary constructor com.tomtom.sdk.datamanagement.nds.update.compositeregion.CompositeRegionsUpdater

The factory function com.tomtom.sdk.datamanagement.nds.NdsStoreFunctions.kt.NdsStore is now available in General Availability.

Update the offline map developer guides with the latest configuration and initialization steps.

com.tomtom.sdk.datamanagement.navigationtile.NavigationTileStore now only accepts URLs with an http or https scheme, preventing configuration errors from unsupported URL schemes.

com.tomtom.sdk.datamanagement.nds.region.RegionUpdater no longer blocks the UI thread, which could previously cause the app to become unresponsive. This includes:

• findRegionsAroundPosition() and findRegionsAlongPolyline() no longer block the UI thread
• calculateUninstallSize() no longer blocks the caller's thread
• calculateUninstallSize() and calculateDownloadSize() now return more possible MapUpdateError values

Fix a rare crash (ConcurrentModificationException) in com.tomtom.sdk.datamanagement.nds.update.compositeregion.CompositeRegionsUpdater that could occur when region-update callbacks were processed concurrently.

Fix an issue where the SDK could not recover from a missing map keystore folder.

Fix several rare crashes that could occur during initialization of the NDS.Live tile store, for example due to unexpected encryption or persistent-cache errors.

Fix an issue where automatic map updates skipped updating regions around the vehicle's current location if a route was already active when updates were enabled.

Fix an issue where the SDK could saturate a CPU core and degrade overall device performance while a map was downloading and no onboard map was yet available.

com.tomtom.sdk.navigation.resumesnapshotrenewer.NavigationResumeSnapshotRenewer no longer saves a navigation resume snapshot in response to com.tomtom.sdk.navigation.RouteUpdatedListener2 events when com.tomtom.sdk.navigation.resumesnapshotrenewer.NavigationResumeSnapshotRenewerOptions.saveInterval is set to Duration.INFINITE.

Setting saveInterval to Duration.INFINITE now disables snapshot saves triggered by route updates, reducing flash storage I/O by avoiding writes for dynamic route data (such as traffic, ETA, or section refreshes) that become outdated once the route is paused. Snapshots are still saved on active route change, waypoint arrival or departure, and navigation start. Unless you were relying on saveInterval being Duration.INFINITE, there is nothing to worry about.

Offline-only navigation can now be set up using the new initialization API.

Simple initialization example:

1tomTomNavigation =
2    OfflineTomTomNavigationFactory.create(
3        Configuration(
4            context = context,
5            apiKey = TOMTOM_API_KEY,
6            locationProvider = locationProvider,
7            ndsStore = ndsStore,
8        ),
9    )

Advanced initialization example:

1tomTomNavigation = OfflineTomTomNavigationFactory.create(
2    Configuration(
3        context = context,
4        apiKey = TOMTOM_API_KEY,
5        locationProvider = locationProvider,
6        ndsStore = ndsStore,
7        betterProposalAcceptanceMode = BetterProposalAcceptanceMode.Automatic,
8        safetyLocationsConfiguration = safetyLocationsConfiguration,
9        hazardsConfiguration = hazardsConfiguration,
10    )
11)

The following APIs are now in General Availability:

• com.tomtom.sdk.datamanagement.nds.update.NdsStoreUpdaterConfiguration.manualUpdateNetworkConfig

com.tomtom.sdk.telemetry.Consent and the com.tomtom.sdk.telemetry.Telemetry.initialize(context, configProvider) overload are deprecated.

Before:

Telemetry.initialize(context, configProvider)
Telemetry.userConsent = Consent.Personalized

After:

1Telemetry.initialize(
2   context,
3   configProvider,
4   locationProvider,
5   initialConsent = UserConsent.TelemetryOn,
6)
7
8// Later, when the end-user changes their preference:
9Telemetry.setConsent(UserConsent.LocationOnly)

Important:

• When using the consent-aware APIs (Telemetry.initializeoverloads that accept initialConsent / getInitialConsent, Telemetry.consent and Telemetry.setConsent), Telemetry must be initialized (or explicitly opted out by setting the consent to UserConsent.TelemetryOff) before using SDK components that may post telemetry events. Otherwise, the application may crash when telemetry events are posted.
• Telemetry initialization can only be performed once. Any subsequent attempt to reinitialize Telemetry will result in an exception.
• Start the LocationProvider updates before initializing Telemetry to avoid warnings.

com.tomtom.sdk.telemetry.RestrictedTelemetryConfigProvider is deprecated and will be removed 6 months after the next release.

com.tomtom.sdk.telemetry.RestrictedTelemetryConfigProvider migration instructions:

Prerequisite:

First, migrate to the consent-aware Telemetry.initialize API, which has its own migration steps. See the Telemetry.initialize deprecation documentation for details.

Before:

 Telemetry.initialize(context, RestrictedTelemetryConfigProvider(context, apiKey))

After:

• Use DefaultTelemetryConfigProvider instead and specify UserConsent.LocationOnly:

1Telemetry.initialize(
2    context,
3    DefaultTelemetryConfigProvider(context, apiKey),
4    locationProvider,
5    initialConsent = UserConsent.LocationOnly,
6)

Behavioral difference:

• Setting the consent to UserConsent.LocationOnly ensures that only location events are allowed, maintaining the same behavior as RestrictedTelemetryConfigProvider.

• It is the integrator's responsibility to limit the end-user consent options to UserConsent.TelemetryOff and UserConsent.LocationOnly. Allowing the end-user to choose UserConsent.TelemetryOn will send all events, which contradicts the use-case of this construct.