Releases: datalogic/scan2deploy-android
Releases · datalogic/scan2deploy-android
2.3.0-c077d97a
Enhancements
- Better coordination with Espresso during Enterprise backup restore.
- Enhanced timeout for OEMConfig to avoid errors when downloading eSIM profiles.
- Supports ability to clear any existing application policies
Corrected Defects
- Applying WPA3 network profiles when Wi-Fi is disabled can fail.
- Unable to create an Enterprise backup when deploying from USB storage.
2.2.4
Enhancements
- Updated to support latest ShopEvolution.
Corrected Defects
- Disabling Wi-Fi in Device Settings can fail when also defining networks configuration.
- Creating Enhanced Open or WPA3-based networks can fail.
- Expanding profile contents can fail when used with ShopEvolution.
2.2.3
Enhancements
- Updated to support Android 13
- Added selection of default browser
- Enhanced support for EAP network configuration
- WPA3 EAP networks
- CA Certificates
- Online certificate status
- Domain filters
Corrected Defects
- Scanning a set of 10 or more v3 labels fails if not scanned in order
- Scanning an invalid profile barcode label presents a blank screen
- Replacing or removing an existing WiFi network fails
Scan2Deploy 2.1.0 (Revision 13011)
The following issues have been addressed:
- Incorrectly reports "Done" after "Checking for archive server" if WiFi is not connected or no network is defined in profile.
- The following failures are now treated as warnings instead of (fatal) errors.
- Failure to update/remove existing networks.
- Attempting to downgrade pre-installed APKs.
- Visual Formatter files are persisted with the wrong persistence type.
- Visual Formatter files are installed but disabled when profile also includes a self-update.
- Profile policies filter out some valid property IDs.
- Agent v2.0.8 fails to complete a self-update to a newer version of Agent.
- Restoring Enterprise backup fails if profile includes a self-update to a newer version of Agent.
- Fails waiting to get a valid IP address under the following conditions:
- No download deployment is used and networks are only defined with "after-staging" availability.
- Location mode is disabled.
- Timeout waiting for OEMConfig when restoring from Enterprise backup.
- Deploying a profile with a keyboard remapping file can result in applying a previous profile.
- Download percentage can display unexpected values with very large profiles.
- Agent attempts to install all ZIP files from the Download folder as an OTA file.
- Reset after OTA update fails when used with silent deploy.
- Disabling Enterprise Agent APK can fail.
Scan2Deploy 2.0.8 (Revision 13010)
Changelog
- Enhanced profile message content. Content is organized by stage and can expand to review details. Previous log can be reviewed and copied from device.
- Improved feedback of multi-label profiles.
- Added feedback from OEMConfig.
- Added feedback from OTA updates.
- Improved script command processing.
- Improved feedback when using Agent service.
- Increased validation of profile contents.
- Increased performance by reducing time to process profile.
- Corrected numerous stability issues.
- Fixed issue where profile manager policies might fail to apply on devices with limited space in the enterprise partition.
- Corrected issue failing to complete deployment when installing Keyboard mapping files.
- Corrected "Unable to reach archive server" error when switching from an existing network connection to a different one defined in a profile.
- Corrected intermittent failures when installing Visual Formatter files.
- Added more filters to avoid misinterpreting short Code-128 labels as old DL-Stager labels.
Scan2Deploy 1.40.3 (Revision 12711)
Changelog
- 173655 - Fixed issue where profile manager policies might fail to apply on devices with limited space in the enterprise partition
Scan2Deploy 1.40.2 (Revision 12710)
Changelog
- 147277 - Fixed issue where deployment could intermittently stall when launching after the SetupWizard process or self update
- 161911 - Increased decompression buffer size to prevent large amounts of data from being truncated in barcode only deployments
Scan2Deploy 1.40.1 (Revision 12599)
Changelog
- 167690 - Fixed firmware update not working
Scan2Deploy 1.40 (Revision 12312)
Changelog
- 166977 - Add field encryption support in Agent
- 165253 - Add wait period for FileSystemManager service to start
Scan2Deploy 1.39.0 (Revision 11899)
Changelog
- 156762 - Apply SDK ProfileManager json files
- 151913 - Scan2Deploy profile cannot be deployed via espresso package (started via intent)
- 160575 - M10 (+MK). Impossible to change status_bar_show_battery_percent" SYSTEM setting via Scan2Deploy (+ S2D agent freeze)
- 144735 - Support Enterprise and Factory Reset persistence options
- 162985 - [S2D 1.7.2] Sometimes cannot Abort when scan2deploy unavailable WiFi encryption mode "Enhanced open"
- 163069 - Final action intent format may be incorrectly identified
- 163068 - Unable to connect to FTP server (external profile hosting)
- 157733 - [Scan2Deploy Agent Support 'Barcode Only' deployment action]
- 162164 - Screen Lock setting changes
- 160301 - Do not fail staging and skip back-up-to-enterprise until it's supported for shop evolution use-case
- 158889 - The 'network.json' file is not in the 'shopevolution\cfg' path
- 108038 - [S2D Agent] Unexpected “Scan2Deploy.archive” file and “Scan2Deploy” folder created after Apply DXU, Install Apps, Datalogic Apps, Scanner Settings and File Upload