Release Notes

All notable changes to this project will be documented in this file.

The format is based on Keep a Changelog and this project adheres to Semantic Versioning.

The API documentation for the current version (16.0.0) is available here.

[16.0.0] - 2026-09-30

iOS: Adopt the Scene-Based Life Cycle for Xcode 27

iOS 27 now enforces the scene-based life cycle: if you build your app with Xcode 27, you must adopt it in your own app. This is an Apple requirement and the SDK cannot do it for you.

See Migrating to the UIKit scene-based life cycle and Transitioning to the UIKit scene-based life cycle.

Changed

iOS

Breaking change: Xcode 27 now rejects deployment targets below 15.0, and an integrator on Xcode 27 will not be able to build against the previous value. Devices below iOS 15.0 are not supported by this release. If your app still supports them, please stay on version 15.5.0.

  • Raised the SDK’s minimum iOS version from 13.4 to 15.0.

Fixed

iOS

  • Fixed landscape scanning in apps built with Xcode 27 and running on iOS 27. iOS 27 enforces the scene-based life cycle, and the app-wide interface orientation the SDK previously relied on no longer reports a usable value there, so in landscape the rotate-device warning stayed on screen and the scan process never started. The SDK now reads the orientation from the view’s window scene. Apps built with Xcode 26 or earlier are unaffected.

  • Fixed the scan screen closing when the app lost focus before a scan had started, for example right after the camera permission was granted on iOS 27.

  • Fixed the torch staying on after closing the scan screen shortly after opening it.

[15.5.0] - 2026-08-31

Changed

Android & iOS

  • No functional changes to the SDK.

iOS

Swift Package Manager is now the recommended way to add the SDK. CocoaPods remains available and is published through 1 December 2026. Versions published before then stay installable indefinitely.

[15.4.0] - 2026-08-26

Added

Android & iOS

  • Tire Sidewall Scanner: the details object in the scan result can now include runflat, threePeakMountainSnowflake (the 3PMSF marking), and mudAndSnow (the M+S marking) when they can be reliably determined for the recognized tire.

Fixed

Android & iOS

  • Response.Error and Response.Exception now provide a human-readable toString(), surfacing the error code, error message, and wrapped exception. Previously, logging these objects directly produced an unreadable default representation (e.g. k3.l@2c19c0a).

[15.3.3] - 2026-07-21

Changed

iOS

  • Tire Sidewall Scanner: more robust camera-preview orientation handling on iPad, particularly in multi-window and split-view layouts.

Fixed

iOS

  • Tire Sidewall Scanner: fixed an issue where the scanner could fail to open on a fresh app installation, showing a black screen until the OS terminated the app after about 10 seconds. This affected installations where camera access had already been granted before the scanner was first opened; subsequent attempts would gradually start working.

[15.3.2] - 2026-07-16

Changed

Android & iOS

  • Tire Sidewall Scanner: the scanner start time was drastically improved, especially on older devices.

  • Tire Sidewall Scanner: more reliable captures when the device moves slightly during the capture.

Fixed

Android

  • Tire Sidewall Scanner: fixed a freeze (ANR) that could occur when closing the scanner during an active scan, and a related rare crash.

  • Tire Sidewall Scanner: fixed an issue where the scanner could open with a black camera preview and never recover.

iOS

  • Tire Sidewall Scanner: fixed an issue where the camera could remain active after the scanner was closed.

  • Tire Sidewall Scanner: fixed the camera preview keeping a stale orientation when the device is rotated directly by 180°.

[15.3.1] - 2026-07-13

Fixed

iOS

  • AnylineTireTread.isDeviceSupported() no longer reports a supported device as unsupported on iOS patch releases (three-component versions such as 18.1.1).

[15.3.0] - 2026-07-08

Added

Android & iOS

  • InitOptions.uploadTimeoutMillis — configurable per-attempt timeout for image uploads, passed to AnylineTireTread.initialize(…​) via InitOptions. Default is 20 s.

  • See Getting Started for usage.

Changed

Android & iOS

  • Reduced the internal retry count for Tread Depth backend requests from 5 to 1. Combined with the new per-attempt timeout, this bounds worst-case wall-clock per image upload to ~40 s at the default settings (previously ~160 s+).

Fixed

Android & iOS

  • Tire Sidewall Scanner: the neon capture overlay now draws for any detected tire, not only the framing-locked case.

[15.2.0] - 2026-06-25

Added

Android & iOS

  • New AnylineTireSidewallScanner API for reading tire sidewalls. It presents a guided, full-screen camera that scans the sidewall automatically once it is correctly framed, and returns the structured reading together with the captured image - so you do not need to integrate the Cloud API yourself.

    • scan() takes the host, your Cloud API client ID, and an optional TswScannerConfig, and delivers the outcome (Completed, Failed, or Aborted) once to the onResult callback on the main thread.

    • isSupported() reports device support before launching, without initializing the SDK.

    • Completed carries the reading (resultJson), the captured image (imageBytes), and TswScanMetadata with the environmentLighting at capture.

    • For full usage, see the Tire Sidewall Scanner guide.

[15.1.0] - 2026-06-12

Added

Android & iOS

  • New AnylineTireTread.isDeviceSupported() API to check whether the current device is supported by the SDK before starting a scan. On Android, it returns the new CAMERA_PERMISSION_DENIED ErrorCode if the camera permission has not been granted.

[15.0.0] - 2026-03-18

Breaking Changes

Android & iOS

  • Replaced TireTreadScanView composable/UIView with AnylineTireTreadScanner().scan(). The scan UI is now launched via a single callback-based method that returns a ScanOutcome.

    • CompletedOutcome replaces onScanProcessCompleted callback.

    • AbortedOutcome replaces onScanAborted callback.

    • FailedOutcome replaces onError callback. Includes an SdkError with structured error information.

  • Replaced exception-based initialization with callback-based AnylineTireTread.initialize() that returns SdkResult<Unit>.

  • Replaced Response.Success/Response.Error/Response.Exception with SdkResult.Ok/SdkResult.Err for all async operations.

    • Access result data via .result (not .value or .data).

    • Access errors via .error which returns SdkError with code, type, message, and optional debug fields.

  • Replaced AnylineTireTreadSdk.getTreadDepthReportResult() with AnylineTireTread.getResult().

  • Renamed API entry points:

    • AnylineTireTreadSdk → AnylineTireTread (runtime: init, results, feedback)

    • Scanner UI → AnylineTireTreadScanner (owns scan() only)

Changed

Android & iOS

  • Replaced ScanEvent and all per-frame event types (OnScanStarted, OnScanStopped, OnImageUploaded, OnDistanceChanged, OnTireWidthProvided) with the ScanOutcome-based scan flow.

  • Replaced startScanning(), stopScanning(), and abortScanning() manual scan controls with AnylineTireTreadScanner().scan().

Removed

Android & iOS

  • Removed countdownConfig, scanDirectionConfig, and tireOverlayConfig from UIConfig.

  • Removed showMeasuringSpots from ScanConfig.

  • Removed all element-level visible properties from the UI configuration model.

    • UI visibility is no longer configured through per-element visible flags.

Added

Android & iOS

  • New SdkError model with 17 ErrorCode values across 5 ErrorType categories for structured error handling. See the v14 → v15 Migration Guide for detailed transition instructions.

[14.0.1] - 2026-01-16

Fixed

Android

  • Fixed duplicate camera permission dialogs.

Android & iOS

  • Internal improvements and bug fixes.

[14.0.0] - 2025-12-15

Breaking Change

Android

  • The legacy bypass on the TireWidthInput screen has been removed.

    • The Tire Width must be provided either via integration or by the user through the SDK’s UI input.

  • The TireTreadSDK has been updated to comply with Android’s new page size requirements as outlined in the Android Developer Guide. This change ensures compatibility with Android 15+ devices that enforce 16KB page sizes.

    • Increased the minimum Gradle version from 8.2.1 to 8.7.

    • Increased the minimum Android Gradle Plugin version from 8.2.1 to 8.5.1.

Android & iOS

  • The useDefaultUi and useDefaultHaptic boolean properties in UIConfig have been replaced with a unified appearance enum property.

    • The new appearance property accepts the supported themes:

      • "Classic" - Classic UI appearance with haptic feedback

      • "Neon" - New neon UI appearance with haptic feedback (default)

    • Migration:

      • Replace "useDefaultUi": true with "appearance": "Neon" (or omit for default)

      • Replace "useDefaultUi": false with your own wrapper-side custom handling instead of a built-in appearance

[13.1.1] - 2025-12-05

Fixed

Android & iOS

  • Hardened HTTP client implementation to ensure reliable network communication.

    • (iOS) HTTP client engines are now configured to prevent conflicts with third-party network interceptors.

[13.1.0] - 2025-11-20

Added

Android & iOS

  • Added movement direction detection to measurement results.

    • The SDK now automatically detects and reports the device movement direction during tire scanning.

    • The movement direction is available through the new measurementMetadata.movementDirection property in TreadDepthResult.

    • Possible values are: Unknown (direction could not be determined), LeftToRight (device moved from left to right), and RightToLeft (device moved from right to left).

    • This information helps understand the scanning orientation and can be useful for result interpretation.

    • See the Results documentation for more information.

[13.0.6] - 2025-11-17

Deprecated

Android

  • The Skip button in the TireWidthInput screen has been deprecated and will be removed in the next major release.

    • The Tire Width must be provided either via integration or by the user through the SDK’s UI input.

Fixed

iOS

  • Improved memory management during the scan process.

[13.0.5] - 2025-11-10

Changed

Android

  • Lowered the minimum required Android API level from 26 to 23.

iOS

  • Lowered the minimum required iOS version from 16.4 to 13.

Fixed

Android

  • Fixed an issue where the OrientationWarning was not properly centered on the screen.

  • Correctly handle capture when device orientation is locked.

[13.0.4] - 2025-09-26

Changed

  • Removed kotlinx-datetime dependency to enable compatibility with React Native v0.84+.

[13.0.3] - 2025-09-04

Fix

Android

  • For XML Layouts, fixed an issue that prevented the tire width to be set via the TireWidthInput screen.

    • With this update, users of the TireWidthInput screen on XML Layouts should also now obtain far more accurate tread depth measurement results.

[13.0.2] - 2025-06-18

Fix

Android

  • Fixed an issue that prevented the tire width to be set via the TireWidthInput screen.

    • With this update, users of the TireWidthInput screen should obtain far more accurate tread depth measurement results.

iOS

  • Fixed NSInvalidArgumentException crash when using both the Anyline Mobile and Tire Tread SDKs in a single project.

[13.0.1] - 2025-06-03

Fix

iOS

  • Fixed an issue that prevented the ScanView from being initialized with JSON configs.

[13.0.0] - 2025-05-19

We have completed a major update to the Anyline Tire Tread ScanView Config classes in version 13.

If you are coming from a previous Anyline version, it is helpful to go over some of the more significant changes in the Migrating from SDK v12.x to v13+ page.

Breaking Changes

Android & iOS

  • The TireTreadScanViewConfig, was now replaced by the TireTreadConfig. This new configuration object includes:

    • UIConfig: Configuration for the user interface.

    • ScanConfig: Configuration for the scanning process.

    • AdditionalContext: Any additional context required for a measurement.

You can find further implementation details in the Scan Process - Overview page and in the API docs.

iOS

  • The ScanViewControllerHolder interface was removed.

    • Starting with this version, the TireTreadScanView creation will directly return an instance of the TireScannerViewController.

    • Remove the ScanViewControllerHolder interface implementation, and directly set the return of the TireTreadScanView creation to the scannerViewController, previously defined by the interface.

    • The dismissViewController can be completely removed, as the dismiss behaviour should be provided by the onScanAborted, onScanProcessCompleted, and onError callback implementations.

  • The context parameter of the TireTreadScanView was removed.

    • It is not necessary to provide your controller’s self anymore.

For more details, check the iOS scan process page.

Added

[12.1.0] - 2025-04-23

Changed

  • The default scan speed is now ScanSpeed.Fast.

    • The scan process will now, by default, take 7 seconds to be completed (instead of 10 seconds).

    • This configuration can still be changed by setting the TireTreadConfig.uiConfig.scanSpeed property to ScanSpeed.Slow.

Added

  • The TireTreadScanView can now also be initialized without any config object/string.

    • In this scenario, the default config values will be used.

    • For more details, refer to the Scan Process - Overview page.

iOS

  • Added support for iOS Simulator builds when using the SPM package

    • While the camera and scanning capabilites cannot be used in the simulator, the package from SPM now can also run on x64 and arm64 simulators, allowing running automated tests, or testing other features in your application.

[12.0.1] - 2025-04-07

Changed

  • Fixed a bug that lead to an exception when deserializing TreadResultRegion from JSON

[12.0.0] - 2025-04-02

Breaking Changes

  • Renamed the parameter jsonConfig of the TireTreadScanView composable to `config

  • Replaced the "minimum value" properties in the TreadDepthResult with a single minimumValue property of type TreadResultRegion.

Android

  • Minimum required Gradle version and AGP version is 8.2.1

  • Removed the custom XML attributes from the TireTreadScanView

Added

  • Permissions required by the SDK are now handled internally

  • Added a new MissingPermission screen to the DefaultUI, which can be configured via the MissingPermissionConfig

    • If DefaultUI is not used, a black screen will be shown, when the user denies camera permission.

  • Added edge-to-edge support in the DefaultUI for Android API 35 and above

Changed

  • For the following API calls we changed the generic IllegalStateException to ScanProcessNotCompletedException in case the scan process wasn’t completed at the time of the API request:

    • AnylineTireTreadSdk.getTreadDepthReportResult

    • AnylineTireTreadSdk.getTreadDepthReportPdf

    • AnylineTireTreadSdk.getTreadDepthReportUrlString

[11.2.0] - 2025-02-28

Added

  • Added the minimum value of the measured tread depths to the TreadDepthResult. You can access it via .minimumValueMm for millimetres or .minimumValueInch and minimumValueInch32nds for inches.

  • Added a hint to inform the user to enable auto-rotation to the OrientationWarning screen. You can configure the text via the OrientationWarningConfig.rotationLockHint property.

[11.1.0] - 2025-02-13

Added

  • Added the possibility to convert TreadResultRegion to and from JSON strings

Fixed

iOS

  • Fixed an issue that would lead to screen stuttering issues under bad network conditions

  • Fixed an issue where haptic feedback would be triggered on the upload screen

[11.0.2] - 2025-02-07

Fixed

Android

  • Fixed an issue where tire width was not passed correctly when initializing the TireTreadScanView in code

  • Fixed an issue where the user was not able to start the scan, if the camera couldn’t provide a focus in time

[11.0.1] - 2025-02-05

Fixed

Android

  • This version addresses a potential crash that could happen on specific scenarios due to Instrumentation Assets not being available.

[11.0.0] - 2025-01-22

Breaking Changes

  • We Split TireTreadScanViewCallback into separate function callbacks to further accentuate the correct flow of information

    • onScanAborted function callback has to be provided now to handle the case when the scan gets aborted

    • onError function callback has to be provided now to handle an error that occurred during scanning

    • onScanProcessCompleted function callback has to be provided now to continue the user flow after the scanning process has finished

    • For more information, check the documentation for Android and iOS

  • Removed onUploadAborted event as it was consolidated into onScanAborted to simplify the communication with the app

  • Removed onUploadFailed event as it was consolidated into onError to simplify the communication with the app

  • Removed onUploadFinished event as it was consolidated into onProcessCompleted to simplify the communication with the app

Added

  • Added new classes representing the various scan events that can happen during a scan

  • The new OnTireWidthProvided event (Android only) notifies when the user provided a tire width or just skipped the step

  • TireWidthInputConfig has new configurable values to customize the user experience

    • Added a new configurable value prefilledInputWidth to prefill the tire width in the text field in the TireWidthInput screen

    • Added a new configurable value tireWidthRange to limit the possible values the user can enter in the TireWidthInput screen

    • Added a new configurable value tireWidthOptions representing the shortcut button values the user can choose from when selecting a tire width in the TireWidthInput screen

[10.0.1] - 2024-12-19

Changed

Android

  • Improve measurement reliability for low-performing Android devices.

[10.0.0] - 2024-12-16

Breaking Changes

Android

  • Renamed the function to initialize the TireTreadScanView from withScanConfig() to init()

Added

Android

  • Added a new screen TireWidthInput to the DefaultUi with its corresponding config TireWidthInputConfig

    • This view allows users to enter the tire width to enable more accurate results

This screen is only available on Android and cannot be configured for iOS.

Changed

  • Deprecated AnylineTireTreadSdk.getTreadDepthReportUrlString() and AnylineTireTreadSdk.getTreadDepthReportPdf()

    • PDF reports are now deprecated and will be removed in the next versions.

  • Enhanced management of lifecycle events during rotation

Android

  • Changed the signature of the TireTreadScanView initialization function to include the TireTreadScanViewCallback to be able to observe events during scan process

  • Changed the signature of the TireTreadScanView initialization function to include a lambda function to observe a failed initialization

Removed

Android

  • Removed the possibility to directly set up the TireTreadScanView via XML attributes to streamline the integrator experience

  • Removed TireTreadScanView.tireTreadScanViewCallback attribute, it can now be set via the TireTreadScanView.init() function

  • Removed TireTreadScanView.onInitializationFailed attribute, it can now be set via the TireTreadScanView.init() function

[9.0.0] - 2024-11-14

Changed

  • Introduced a new and improved DefaultUI, that is more streamlined to provide the user a simpler scanning experience with less friction. Changes include:

    • New icon and default text for the OrientationWarning for a sleeker experience

    • New icon and default text for the TapToStartScanningTooltip to be a more prominent guiding experience

    • TapStoStartScanningTooltip now also makes the user aware when they have to move the device before starting the scan

    • Added a new animation to the FocusPointTooltip to better visualize how to get to a focussed camera quicker

    • Introduced a more prominent Countdown that shows how many seconds are left until the scan is done

    • Introduced a visual guide in ScanDirection to show the user in which direction he should move the device for an optimal scan result

  • Introduced a custom tag during SDK initialization to identify different devices of the same model

    • This feature is experimental and only meant for internal use

  • Using the DefaultUI does not block the user from starting the scan, if the distance to the tire is not optimal (around 20cm or 8in)

Breaking Changes

  • Removed LineProgressBar and LineProgressBarConfig to be in line with the new DefaultUI

  • Removed HowToScanTooltip and HowToScanTooltipConfig to be in line with the new DefaultUI

  • Removed ProgressTimer and ProgressTimerConfig to be in line with the new DefaultUI

[8.0.1] - 2024-11-05

Fixed

  • If the internet connection becomes unavailable before the scan is started, the TireTreadScanView will now handle it by invoking the onScanAbort callback.

[8.0.0] - 2024-10-10

Fixed

  • Fixed a crash that happens when requesting the result report with an invalid UUID

Breaking changes

Android

  • The companion object (AnylineTireTreadSdk.companion) for calling the functions was removed to provide a better integrator experience (an example of its usage can be found here)

iOS

  • Removed the unnecessary context parameter from the SDK initialisation. The SDK can now be initialised with just the license key (an example implementation can be found here).

  • The object for calling the functions changed from AnylineTireTreadSdk.companion to AnylineTireTreadSdk.shared (an example of its usage can be found here)

[7.0.0] - 2024-09-23

Added

  • Added correlationId to additionalContext to allow the integrator to tie their other Anyline scan processes to the tread depth measurements from the TireTreadSDK

  • Updated internal JSON parsing to allow for optional values in responses

Breaking changes

  • Removed function to send tire width after the scan (AnylineTireTreadSDk.sendTireWidthResultFeedback), as there is now the possibility to send it with the scan

  • Removed unneeded confidence from TireTreadResultRegion.initGlobalMm and TireTreadResultRegion.initGlobalInch

[6.1.1] - 2024-09-12

Fixed

Android

  • Fixed an issue that could lead to less images being processed during the measurement

[6.1.0] - 2024-09-06

Added

Android

  • Added an option to pass the width of the tire when initializing the scan process to further improve the accuracy of the measurements

    • an example of how this is implemented can be found here.

    • For now this feature is meant for passenger car tires only

Fixed

  • Fixed an issue where an unavailable region in the TreadResultRegion would be presented as available with 0.0 as a fallback value.

[6.0.0] - 2024-08-20

Added

  • Added the SDK’s API documentation detailing the functions and interfaces the integrator can use

  • Added an Orientation Warning to the Default UI making the user aware to hold the device in landscape mode for an optimal scan experience

Breaking Changes

  • Reworked the way results from network requests are handled: instead of two callbacks (one for failure and one for success) only one is needed to be passed as a parameter (an example of how this works for fetching the result can be found here)

[5.2.0] - 2024-06-17

Added

  • When initializing the scan process with a JSON config, you can now listen for possible error messages with a callback method. This is not supported when initializing via view.xml.

Changed

  • Scanning is limited to landscape mode of the device to improve the scanning experience.

Fixed

Android

  • Fixed a potential crash that could happen when keeping the ScanView open for several minutes.

[5.1.0] - 2024-05-28

Added

  • Scan process can now also be set up using a full JSON string as the configuration input

    • For instructions, check the platform specific scan process pages for Android and iOS

[5.0.0] - 2024-05-24

Please be aware of the breaking changes listed below.

Added

  • Scan process can now be set up via a JSON configuration

    • For instructions, check the platform specific scan process pages for Android and iOS

  • Scan result can now easily be converted to a JSON for further processing on integrator side

    • Simple use the toJson() extension function in the TreadDepthResult object

Changed

  • Configuring the TireTreadScanViewConfig is more intuitive now.

Removed

  • Replaced some functions of TireTreadScanViewConfig with a single function withScanConfig() to make the setup process more streamlined.

Breaking changes

  • Removed the Builder from the TireTreadScanViewConfig. The configuration can be now done directly using the fields of a TireTreadScanViewConfig object.

    • Builder.withScanSpeed is now tireTreadScanViewConfig.scanSpeed

    • Builder.withAdditionalContext is now tireTreadScanViewConfig.additionalContext

    • Builder.withMeasurementSystem is now tireTreadScanViewConfig.measurementSystem

    • Builder.withCustomDefaultUiConfig is now tireTreadScanViewConfig.defaultUiConfig

    • Builder.disableDefaultHaptic is now tireTreadScanViewConfig.useDefaultHaptic

    • Builder.disableDefaultUi is now tireTreadScanViewConfig.useDefaultUi

[4.2.1] - 2024-04-23

Changed

  • Improved communications with our backend to offer a more stable and reliable scan experience

[4.2.0] - 2024-04-05

This release introduces several enhancements to the Default UI, resulting in a more accurate and intuitive scanning process. Additionally, the Default UI now supports localization and customization.

Check the Default UI specific documentation for more details.

Added

  • A new DefaultUiConfig class now allows fine-grained customization of the Default UI’s components.

    • In the component configuration classes, visible properties enable you to selectively hide specific elements while keeping others visible.

    • text properties can be used to define custom texts for the components.

    • Check the Default UI’s Customizing and Elements page for customization options, a detailed list of components, and their respective configuration classes.

Changed

  • Default UI

    • Introduced timer and moving phone icon to guide the pace and direction of the scan

    • Improved upload screen

    • Moving tire overlay adapts automatically to the orientation of the device

Make sure to always scan from outside to inside, when scanning a tire mounted on a car

[4.1.0] - 2024-03-08

This release introduces several improvements to the Default UI’s user experience and scan guidance. Additionally, it includes a new feature that allows for providing and retrieving more context for measurements. A small bug fix has also been implemented for Android.

Added

Android & iOS

  • [Default UI] Introduced a tire-shaped grid overlay to the Default UI, making it simpler to align the camera correctly with the tire’s shoulder.

    • The speed and direction to where the phone should be moved during the scan process are now guided by the tire-shaped overlay’s movement.

    • The scanning process should always be performed from the outer side to the inner side of the tire.

    • When the phone is rotated, both the overlay and the scan direction are automatically adapted.

  • [Default UI] Added a tooltip informing the user how to position the tire overlay to be in line with the shoulder of the tire.

  • [Additional Context] A new class AdditionalContext was added to enable holding more context about a specific measurement.

    • This information can be provided when initializing the TireTreadScanView.

    • If provided, its information will be returned in the measurement’s result.

    • Check the platform-specific 'scan process' documentation pages for more information.

  • [Scan View] The TireTreadScanViewConfig builder has a new .addAdditionalContext(AdditionalContext) function, enabling you to provide more context to a measurement.

  • [Result] Added a new property called measurementInfo (of type MeasurementInfo) to the TreadDepthResult class.

    • This class can be used to retrieve more information about the measurement such as UUID, status and additionalContext (if previously provided).

iOS

  • [Default UI] Added a small in-between screen to guide the user on how to focus the camera.

  • [Default Haptic] Added haptic feedback to signalise that the tire is now in focus.

Removed

  • [Default UI] As part of the user guidance improvements, the tooltip messages on the top of the UI were removed.

Fixed

[Android]

  • Fixed an issue where the distance feedback would continue to be played after leaving the Scan View.

    • In some specific scenarios, the TireTreadScanView's distance feedback would continue to be played even after ending the scan process.

    • With this release, users will not experience this issue anymore, regardless of how the TireTreadScanView is implemented.

[4.0.1] - 2024-02-26

Fixed

[iOS]

  • [Default UI] Fixed a crash that happened when some resource files were not available.

    • When using the Default UI without the image resources available in the Application’s bundle, the SDK would crash.

    • The SDK now includes those resources, preventing any such crashes.

[4.0.0] - 2024-01-25

Please be aware of the breaking changes listed below.

Changed

  • Default UI redesign

    • We reorganized the UI to offer a better user experience with the help of tool tips.

    • The Default UI now intercepts user touches to start and stop the scan process instead of using buttons.

    • We also updated the distance indicator to tell the user whether they have to move closer or farther away from the tire.

  • The DistanceStatus enum has a new status (UNKNOWN on Android - unknown on iOS), returned when no distance information is available.

    • This is the case when the device’s camera was not yet able to focus on the scan target.

Added

  • Added a new captureDistanceStatus property to the TireTreadScanner instance, of type DistanceStatus.

    • This property can be used to check if the user has the device correctly positioned for the scan process.

  • Added a tooltip icon that signalises that the camera is in optimal position to start the scanning process

Breaking Changes

  • To offer a more streamlined experience, we removed some of the classes:

    • Color

    • ATDSideButton on iOS

    • DistanceFeedbackView

    • ScanGuideView

    • ScanSideButtonsView

[3.0.1] - 2024-01-17

Fixed

[Android]

  • Fixed a crash that happened when aborting a scan that wasn’t started yet.

    • Aborting a scan process before starting it would result in crash due to an unitialized property.

    • The SDK will not crash anymore when aborting scans before their initialization.

[iOS]

  • Fixed a crash that happened when the ProximaNova-Bold font was not available.

    • When using the Default UI without the ProximaNova-Bold font available in the Application, the SDK would crash.

    • The SDK’s Default UI will not crash anymore when this font is not available.

[3.0.0] - 2023-12-28

This major release includes many improvements in the usability and stability of the Tire Tread SDK (both for integration and usage).

Please be aware of the breaking changes below:

Breaking changes

[Android & iOS]

  • Scan → TireTreadScanViewConfig

    • defaultUi and defaultHaptic are now enabled by default.

    • The TireTreadScanViewConfig constructor was changed to a Builder pattern, as shown below:

      • TireTreadScanViewConfig.Builder().build() - For more details and examples, check the platform-specific "Scan Process" pages.

  • Results → getTreadDepthReportResult:

    • You no longer need to call getTreadDepthReportResult repeatedly until the measurement result becomes available. Just call the function on a background thread, and listen for callbacks on success and on failure.

    • getTreadDepthReportResult function is now void.

    • getTreadDepthReportResult's success callback has been renamed from Succeed to Succeeded.

    • onGetTreadDepthReportResultSucceeded callback now provides the result as a TreadDepthResult object.

    • onGetTreadDepthReportResultFailed callback now provides the failure information as a MeasurementError object.

  • Results → TreadResultRegion object:

    • The field confidence was removed.

  • Results / PDF Report → getTreadDepthReportPdf function:

    • This function is now void.

    • The success callback has been renamed from Succeed to Succeeded.

    • The onGetTreadDepthReportSucceeded callback provides the ByteArray of the PDF Report.

    • The onGetTreadDepthReportFailed callback provides now only an Exception.

[iOS]

  • Increase minimum iOS version requirement to 16.4.

[Android]

  • The minimum version requirements have been increased to:

    • JDK 17

    • Gradle 8.1.0

    • compileSdk 34

    • minSdk 26

    • Compose Compiler v1.5.0

  • Scan → TireTreadScanView

    • The attributes useDefaultUi and useDefaultHaptic of the TireTreadScanView have been renamed to disableDefaultUi and disableDefaultHaptic respectively, with default values set to false.

      • Default UI and Haptic will be enabled by default, unless explicitly disabled.

Added

[Android & iOS]

  • Audio feedback can now be played by the SDK together with the vibration feedback. For more details and examples, check the platform-specific "Scan Process" pages.

[Android]

  • start, stop, and abort buttons, to SDK’s default UI.

  • capture distance info to SDK’s default UI.

  • capture progress bar, distance feedback, and upload screen to the default UI.

Improved

[Android]

  • Scan is now automatically aborted when the activity containing the TireTreadScanView enters the onPause state.

[iOS]

  • Greatly improve the stability and responsiveness of the SDK.

Fixed

[iOS]

  • Torch sometimes was not activated when starting a scan.

  • Crash when Haptic Engine was not available.

[2.3.0] - 2023-10-25

  • In the TreadDepthResult, a new field valueInch32nds is now available, containing the result in 32 seconds of an inch.

[2.2.0] - 2023-10-09

  • [Android] Added audio feedback in form of a beep when the tire is too far or too close to the camera

  • [Android] Added haptic feedback when the tire is too far or too close to the camera

[2.1.4] - 2023-10-05

Fixed

  • [iOS] useDefaultUi when false is showing black screen

  • [iOS] scan can start even when focus dot has not yet been added

  • [iOS] start/stop button state not updating correctly

[2.1.3] - 2023-08-24

Changed

  • More scan process and image quality improvements

[2.1.2] - 2023-08-24

Changed

  • [Android] Improve scan process and image quality

[2.1.0] - 2023-08-04

Added

  • [Android] Distance info in the default UI

  • [Android] Provide vibration feedback

[2.1.0] - 2023-07-20

This is the first release for iOS

[2.0.0] - 2023-06-27

  • Major rewrite of the SDK (available only for Android)