Esper Release Notes – DevRel 62

In DevRel 62, we have made improvements in identifying different devices while provisioning and enhanced Content management. We’ve made some additions to the Template and Compliance Policy and added a few more features. Here is a list of what’s new:

  • Support for provisioning the devices with the same Serial number 
  • Disable Bluetooth policy in the Template or Compliance Policy
  • Restrict Wi-Fi page from Android settings
  • Ability to store files anywhere in the public directories or the storage
  • Add a widget to the device’s home screen

1. Support for Provisioning the Devices with the Same Serial Number

Esper considered the serial number unique, and if a second device with the same serial number gets provisioned, we used to override the first provisioned device. A combination of Brand, Model, Serial number in Hardware Info, and IMEI 1, IMEI 2 were considered to identify the device uniquely. In some ODM devices, these values are similar or null, and provisioning the device again would override first.

Now, in addition to the above parameters, Esper also considers Wi-Fi Mac ID and Ethernet Mac ID to create a unique device on our dashboard. Please contact Esper support to get the latest Esper Agent version for this feature to work. 

2. Disable Bluetooth Policy in the Template or Compliance Policy

The Bluetooth setting has been added when creating/editing a compliance policy or a template. The IT admin can now edit/create a template or a compliance policy to enable or disable the end-user to configure and use Bluetooth on their device.

Please contact Esper support to get the latest Esper Agent version for this feature to work. 

3. Restrict Wi-Fi page from Android Settings

Esper has introduced disabling the Wi-Fi access point page under the Android settings. IT admin can choose not to allow their end-user to configure Wi-Fi using Android settings. Once enabled, the users cannot add/remove the Wi-Fi access point from the Android settings application. 

Note: By default, this feature will be disabled so that Wi-Fi will be accessible to users. To enable this feature and get the latest Esper Agent version, please contact Esper support

4. Ability to Store Files Anywhere in the Public Directories or the Storage

Esper Agent can now save files in directories where the existing mechanism does not allow. The directories include anywhere in internal storage, public directories, and removable storage.

When the user wants to store some content on the device, the path usually looks like this:

/storage/emulated/0/Esper/NewFolder/

If a device receives the above path and doesn’t have permission, we immediately return a failure message saying the device doesn’t have permission. With the new change, Admin can append the path with the “forced/” keyword (“forced/storage/emulated/0/Esper/NewFolder/”), which will ask users permission for that directory (if the directory exists). On granting access, the files will be saved. 

Note: This is a one-time procedure for each directory. Once permission is granted, the folder and its child folders can be accessed to save files. 

On devices running Android 10 or below, it is advised that the admins inform the users to grant permissions to the root folder to have permission to access all the directories. A new Esper setting, “Storage,” has been added to help users grant permissions to any directories on the device. 

On Android 11 devices, permission cannot be granted to the root folders and download folder.

Please contact Esper support to get the latest Esper Agent version for this feature to work. 

5. Add a Widget to the Device’s Home Screen

Esper now supports adding application widgets on the device home screen. Please contact Esper support to enable this functionality for your environment.

Bugs and Improvements

  • We have added a drop-down to choose from a previously added list of tags while adding a tag on a device. 
  • Previously, Esper Agent would send a success message to the UI when installing an application with the same version but a different signature. Now, Esper Agent checks for failure when the same application version is installed on the device with a different signature. 
  • Increased the screenshot resolution from 10 x 2160 pixels to 10 x 3840 pixels. 
  • Esper device SDK now uses the latest versions of AndroidX libraries as dependencies. This will reduce the compile time for applications using esper SDK.

And that’s it for DevRel 62. Esper’s team is working to deliver another batch of exciting features and improvements in DevRel 63 and beyond. It is scheduled for the first week of July 2021. Please reach out to share your thoughts on how Esper can improve your customer experience in future releases. 

0