Skip to main content

Esper Release Notes - DevRel 189

Date: May 11, 2026

Esper Agent Version: 11.0.3554

New Features 

  • Android 16 Remote Viewer support: You can now remotely view Android 16 devices. 
  • We now support Apple TV You can now provision Apple TVs for digital signage, lobby screens, and more. Provision Apple TV (tvOS 11+) to the Esper console via Apple Business and get access to the following features: 
    • Manage app deployments: Add tvOS-supported apps from Apple Business directly to a tvOS device using a blueprint. Lock down devices to a single app or push an update to all your devices at once. 
    • Save system updates for later: Defer software updates for up to 90 days. Save updates for low-traffic windows.
    • Troubleshoot with quick actions: Switch from kiosk mode to multi app (or vice versa)  to diagnose bugs or send a reboot directly from the console. 
    • Ready to get started? See all the devices in the tvOS help article. 

  • Switch from Multi-app to Kiosk Mode for iPhones, iPads and Apple TVs: Previously, switching from multi-app to kiosk mode (or vice versa) required a blueprint update for iOS and iPadOS devices. You can now achieve the same behavior via a button in Quick Settings for the Apple devices we support. Much like its Android equivalent, switching from multi-app to kiosk mode enables you to troubleshoot issues, without affecting every other device on that blueprint.  Note: Not available for web clips or preloaded apps. 

    Screenshot 2026-05-08 at 1.16.46 PM.png
  • DEP profile configuration for iOS/iPadOS: You can now choose the steps for DEP profiles at the tenant level. Planning to roll out iPhones or iPads devices to your sites? Use the DEP profile configuration API to create a uniform setup experience for every iOS device that will be provisioned to the tenant.  See Apple’s documentation for a list of available skip keys. Requires Apple Business and supervised devices.

Create or Update: 

curl --request POST \
  --url https://{tenant}-api.esper.cloud/api/tenant/v0/depprofiles \
  --header 'authorization: Bearer API_KEY' \
  --header 'content-type: application/json' \
  --header 'x-tenant-id: ENTERPRISE_ID' \
  --data '{
    "show_setup_items": [
      "Appearance",
      "Diagnostics",
      "AppleID",
      "Biometric",
      "Passcode",
      "Privacy",
      "TOS",
      "ScreenTime",
      "Welcome",
      "Intelligence"
    ],
    "auto_advance_setup": true
  }'


Get Current DEP Profile for Tenant: 

curl --request GET \
  --url https://{tenant}-api.esper.cloud/api/tenant/v0/depprofiles \
  --header 'authorization: Bearer API_KEY' \
  --header 'content-type: application/json' \
  --header 'x-tenant-id: ENTERPRISE_ID'

Note: The tenant-level DEP profile configuration expects a JSON payload. When configuring at the blueprint-level, use a property list (PLIST). 

  • You can now edit managed configurations for a group’s iOS application:  Need to apply a one-off change to a group’s application? Edit that application’s managed config file in its group settings. 
     
  • Android Esper Agent Updates: 
    • Fixed an issue where Remote Viewer would time out for some Zebra devices. 
    • Fixed an issue where some supervised capabilities were not working properly with Lenovo devices on Android 16. 
    • We’ve further locked down Android devices that use a lock and password set in a blueprint. When on the password screen, users will now only be able to set a password instead of having access to Android’s default settings. 

Bug Fixes and Improvements

  • We've improved reliability when converging a large number devices with VPP apps. 
  • The geofence name is now shown for template-provisioned devices, consistent with blueprint-provisioned devices. Previously, a missing field appeared in the device’s overview page when it was assigned a geofence and on the Templates experience. Now, you’ll be able to reference the device’s geofence no matter the Blueprints or Templates experience.
  • We fixed an issue where a version_code and version_name mismatch error occurred when editing or cloning a blueprint when app versions were updated. Cloning or editing a blueprint will now be possible regardless of app updates. 
  • We fixed an issue where blueprint API requests would fail when only the app version ID was changed in a blueprint. 

We’re excited to launch DevRel 189 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.

Featured content