Event Feed and Activity Feed missing App Version and App Type when installing apps via API

Android

Title: Activity Feed missing App Version and App Type for API-installed apps

When apps are installed on devices using the Esper API, the Activity Feed may show the installation event but leave the App Version and App Type columns blank.

Why this happens

The Activity Feed populates App Version and App Type from fields in the API request payload. If those fields are omitted from the request body, the installation command is still processed, but no version or type data is recorded against the event.

Steps to fix

1. Confirm the issue is API-specific. Navigate to Devices & Groups → [Device Name] → Activity Feed and locate the affected installation event. If the same app installed through the Esper Console UI shows populated fields, the root cause is a missing payload field, not a display bug.
2. Update your API request payload to include both app_version and app_type fields before calling the install endpoint (POST /v0/enterprise/{enterprise_id}/devices/{device_id}/commands/). The app_type value must be one of PRIVATE, GOOGLE, or PRELOADED — whichever matches the app being installed. Including these fields ensures the event pipeline has the data it needs to populate the Activity Feed columns.
3. Trigger a new installation event using the updated payload. Do not rely on the existing event to retroactively update; a fresh API call is required to generate a new Activity Feed entry with complete data.
4. Open the Activity Feed in the Esper Console by navigating to Devices & Groups → [Device Name] → Activity Feed and locating the new installation event.

Verify: The new installation event should display populated App Version and App Type values within the Activity Feed immediately after the command is processed. Previously created events will remain blank — only events generated with the corrected payload will show complete data.

If this doesn't resolve it

If App Version and App Type are still blank after including both fields in the payload, collect the following before contacting Esper Support:

• The full API request body and response payload for the affected installation command
• A screenshot of the Activity Feed entry showing the blank fields
• A screenshot of the same app installed via the Esper Console UI, confirming that version and type display correctly in that context

This information allows the support team to determine whether the issue is in the request, the event pipeline, or the Activity Feed display layer.

Still need help?

If the steps above don't resolve the issue, submit a support ticket with your device model, Android version, Esper Agent version, and a description of what you've already tried — this helps the support team investigate without a follow-up.