Dates: July 7, 2025
Esper Agent Version: Previously 8.7.1455, now 8.7.1516 as of July 14, 2025
For this release, we’ve merged DevRel 166 with 167.
Updated: July 14, 2025
New Features
- App Size, name, and logo placement. Introducing device name and Esper logo placement. You can now choose where the device ID (and alias if you’re an alias sort of person) and the Esper logo appear on the device. Choose from the top left, top right, bottom right, or bottom left of the screen. Test out these features in a blueprint in Display & Branding and Apps & Configuration sections.
- Added Clear Cache for Google Play Store: You can now clear the Google Play Store’s data and cache from a device’s application page. After converging your device, the application will appear in the device list in Device > Apps and in the blueprint’s preloaded apps section as "com.android.vending". This app’s visibility will continue to be controlled in a blueprint’s Platform Services section. After enabling Google Play Store Visibility, you can clear its cache and data which can help when troubleshooting Play Store issues.
- Added Brand to Get All Devices API: We’ve added the brand key to the get all devices V2 API (your_tenant-api.esper.cloud/api/v2/devices/). See it in the Get all devices in the tenant API.
- We’ve added the following columns to the Devices & Groups page:
- Brand
- Manufacturer
- Wi-Fi Mac ID
-
Added New Dashboard Widget: We've added a new OS type widget to the dashboard so you can see your fleet's operating systems at a glance.
Bug Fixes and Improvements
- We’ve made it possible to converge devices to blueprints with “empty settings” (meaning all the settings are set to the Ignore policy). We’ve also added a message in the event feed each time this occurs to let you know why the converge was successful.
- We fixed an issue where the serial number sometimes wouldn’t appear in the nested JSON of the Get All Device V2 response. You’ll now see the serial number in both the top-level and in the nested values.
- Fixed an issue where the Devices & Groups page would incorrectly display devices in drift even though the device details page showed the correct drift state. This was due to a mismatch in the two drift services. Going forward, there will be a single source of drift information, ensuring all sources show the correct drift state.
- We fixed an issue where some devices would enter a drift state after provisioning. This was because provisioning failed, but the converge command would incorrectly remain in the in progress state. We’ve fixed this, so now the converge command will be updated if provisioning fails. This behavior will only apply to new converge commands that encounter this issue, and will not impact or modify the current state of devices already in this state.
- We’ve added a validation step to the DEP sync process for iOS devices. If a user mistakenly registered an entry for iOS using an Android serial number, and later provisioned the device, it will now be unaffected by DEP syncs.
- Esper Agent improvements:
- Added better error messages for the Esper Agent command related to the apps. Now, a link to the documentation is provided when an error occurs, making it easier to troubleshoot issues.
- Fixed an issue that could lead to increased internal storage usage on certain devices.
- Fixed an issue that could lead to intermittent battery drain on some devices
- We have added a new onboarding state for DPC called SYNC_PACKAGES. This state enables package synchronization with the cloud, addressing the delay in updating the DPC version. As a result, it resolves issues where converge commands were failing previously.
- Added app ordering support in the Esper Agent for app icons, device name, and alias and customized sizing support
- Update for July 14, 2025: After DevRel 167 was released we noticed that alias names tended to disappear when used alone with application customization. We fixed this, so now alias names should display properly when using this features.
We’re excited to launch DevRel 167 over the coming days, and the Esper team is hard at work on the next release. Please contact Esper Support to share your thoughts on how Esper can improve future releases.