Changelog
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.
Build Information
-
Anyline
-
Android SDK: 43.1.0
-
iOS SDK: 43.0.0
-
-
Microsoft Visual Studio For Mac: 17.3.7
-
Xamarin
-
Android: 13.0
-
iOS: 14.6.0
-
-
Xcode Version: 14.2
-
NuGet Version: 6.2.2
Breaking Changes
This release introduces fundamental changes & improvements to how the Anyline SDK works. To upgrade from a prior SDK version to version 43.0.0, check out the migration guide. |
Document Scanner Support Dropped
As of Anyline v43, the Document Scanner plugin has been removed and the feature will no longer be supported. |
Android
Added
-
Added
PluginResult
for describing result data-
Added a type of plugin result for each scanning capability
-
-
[Tire] Added tire size specification fields to the result
-
[Barcode] Added AAMVA parsing for PDF417 codes on driving licenses
-
[ID] Restructured ID results in a way that every field can contain date- & multi-language information
Changed
-
Changed the SDK architecture from one using inheritance & generics to a composition-based approach
-
Instead of distinctive subclasses such as
MeterScanViewPlugin
,IDScanViewPlugin
, etc. the SDK offers anScanViewPlugin
class regardless of the scanning use case
-
-
Changed the structure of how scanning use-cases are constructed through JSON
-
Introduced configuration types for every scanning use-case with a corresponding result type
iOS
Added
-
Added
ALPluginConfig
for describing configuration data-
Added a type of configuration for each scanning capability
-
-
Added
ALPluginResult
for describing result data-
Added a type of plugin result for each scanning capability
-
-
[Tire] Added tire size specification fields to the result
-
[Barcode] Added AAMVA parsing for PDF417 codes on driving licenses
-
[ID] Restructured ID results in a way that every field can contain date- & multi-language information
Changed
-
Changed the SDK architecture from one using inheritance & generics to a composition-based approach
-
Instead of distinctive subclasses such as
ALMeterScanViewPlugin
,ALIDScanViewPlugin
, etc. the SDK offers anALScanViewPlugin
class regardless of the scanning use case
-
-
Changed the structure of how scanning use-cases are constructed through JSON
-
Introduced configuration types for every scanning use-case with a corresponding result type
Improved
-
Added
ScanViewFactory
class targetting the most common use cases -
Cleaned up public interface: also, added memberwise initializers to XXXConfig classes
-
Made additional improvements to stability