Scandit Data Capture SDK 6.2 Release Notes (March 20th 2020)
See also the System Requirements of the Scandit Data Capture SDK across all platforms.
Previously when disabling :type:’barcode.BarcodeCapture’ the session was not cleared. This has been changed such that every disabling of the capture mode clears the session as sessions are not meant to span over multiple enabling and disabling of a capture mode. Make sure that you are handling this correctly, especially when:
You set the duplicate filter to -1. Barcodes will be scanned again after disabling and re-enabling the mode.
You are for some reason disabling and re-enabling :type:’barcode.BarcodeCapture’ during the callback. Make sure this is really needed and adjust your logic if it was dependent on the session never ending.
Significantly improved PDF417 recognition. The PDF417 reader is now better at:
Handling PDF417 codes for which both the start and end delimiter patterns are heavily damaged.
Dealing with erasures and codes that are slightly bent.
Handling codes close to the camera’s resolution limit.
Fixed an issue that caused the barcode scanner to crash upon decoding a PDF417 code with a macro control block without optional fields.
Fixed an issue where installing the plugin in a project on a Windows development machine failed
Fixed an issue with changing the brush and with returning the default brush even if a listener specified a different brush for BarcodeTrackingBasicOverlay.
Fixed an issue where the viewfinder didn’t change its center when the scan area margins were changed.
Fixed an issue on Android that would cause scanning to stop after putting the app in the background and opening again.
Fixed an issue related to a deadlock that would cause the app to be unresponsive.
No deprecations have been made up to this point.
Bugfixes in Scandit Data Capture SDK 6.2.2 (April 15th 2020)
Fixed a very rare infinite loop in the QR code reader.
Bugfixes in Scandit Data Capture SDK 6.2.1 (March 26th 2020)
Fixed an issue that caused unnecessary architectures to be part of iOS exports.
Fixed an issue with Swift 5.