3.0.0

After a lot of work, enioka Scan 3.0.0 is available.

First of all, many thanks to @VincentKobz who helped a lot with this release.

Version 3.0.0 has a limited amount of new features and is instead focusing on improving the developer and user experience, and polishing existing systems.

Breaking changes

To get straight to the point, these are the elements that will require attention when upgrading to version 3:

• maven artefacts have been renamed and their content has changed, more details below in the "Changes to the project structure and maven artefacts" section.

• the Camera API and provided scanner activity received a lot of changes, and their interactions may not transition seamlessly from version 2 to version 3. Make sure to properly test your application if you use these features.

Other APIs remain unchanged and should keep working after upgrading.

Official documentation

With this release, enioka Scan now has a proper ReadTheDocs documentation, which contains helpful information about the library's APIs, maven artefacts, supported devices and even a quick-start guide. It is now easier than ever to develop with enioka Scan, or contribute to it.

Rework of the demo application and release on the Google Play Store

The demo application (demoscannerapp/), which was so far only used for testing, was completely reworked to be usable as a standalone app for users who only need a barcode reader. Its interface is cleaner, and it now properly showcases the library's capabilities. For developers, its source code can be used as a base for your own integration of the library.

The app is now available on the Google Play Store. Also, the associated bundle (.aab) is available to download from the GitHub release page instead of the library's core .aar file, which is now no longer usable on its own (see below).

In order to be published on the store, the demo app now targets SDK 34, which is quite a jump from release 2's SDK 28 target. Due to this, some parts of the demo app might not work as expected on every device. If you spot any bug, feel free to open an issue about it.

Changes to the project structure and maven artefacts

The project structure was heavily refactored for this release, and maven artefacts have been modified as well. This was done to allow developers to only include the features they actually need, without enforcing a "default" content.

This means the upgrade from version 2 to version 3 will not simply be a bump in version number, you will need to go over the dependencies. For example, the core of the library was renamed from com.enioka.scanner:scanner to com.enioka.scanner:enioka-scan-core, and no longer includes any compatibility SDK by default, not even the camera support.

Make sure to check the documentation to know which artefacts you need to include for your needs.

Note that version 2 will no longer receive any new feature or bugfixes. Application-breaking bugs may get addressed, but you should upgrade to version 3 if possible.

Changelog

• API: Extract all SDKs from the core module of the library, and release them as separate artefacts
• API: Add more symbologies to the library's internal support list
• API: Add more scanner search options
• Activity: Migrate to Android X
• Activity: Rework interactions with the camera SDK to account for its rework
• Camera: Rework camera SDK to be closer to regular scanner SDKs
• Camera: Add programmatic control of the camera view's target size and position
• Camera: Add options to pick which distortion mode to use (between crop, stretch and black bars)
• Camera: Fix many lifecycle problems which caused crashes and invalid states
• Camera: Fix preview resolution selection for landscape mode and low-resolution devices
• Demo App: Rework demo application UI and features, it is now usable as an actual app
• Demo App: Release app on the Google Play Store
• Doc: Add ReadTheDocs documentation

As always, you can report any bug or request features via GitHub issues !

2.4.8

Zebra Datawedge Scanner now better detects Datawedge profile changes to properly switch back to the current app's

2.4.7

• Zebra Datawedge Scanner will no longer handle Datawedge notifications when paused
• Zebra Datawedge Scanner will now disable its own profile's scanning capabilities instead of the whole Datawedge service when paused
• Add QRCODE and AZTEC to symbologies supported by the Zebra Datawedge Scanner

2.4.6

Fix symbology selection for camera

2.4.5

Fix crash in Zebra DW provider

2.4.4

Enable all symbologies in the OSS Zebra SDK

2.4.3

Fixed the handling of non-support for torch modes in CameraV1

2.4.2

New features

• Add public method resetTargetPosition() to CameraBarcodeScanView to reset the target to the middle of the screen

Fixes

• Add null guards to prevent Camera V2 from crashing in the event the holding view is being destroyed before the init process completes.
• Fix orientation detection in resolution finder for Cameras, and prevent resolutions higher than the device's display, which should prevent stretching when app:previewRatioMode setting is set to "fitToPicture".

2.4.1

Add null guards in camera implementations to prevent null pointer exceptions.

2.4.0

Camera scanner

• Add method to fetch the image of the latest successful scan
• Add pause toggle to default camera activity
• Add different target color when the camera is paused
• Add lower resolution limit to adaptive resolution
• Add autofocus refresh when target is tapped or moved
• Fix autofocus to properly fit the target for Camera2
• Fix refresh rate for Camera2
• Remove device-specific camera hacks

Zebra scanners

• Add Datawedge provider
• Fix support for devices that use a different type of ACK with the SSI protocol (affects ZebraOss ATT and SPP SDKs)

Misc

• Add a helper method to check and request necessary permissions for the library
• Fix ScannerCompatActivity overriding scanner search options given to it through intent extras