Getting the best out of automating the App Feedback action?Solved

Hey @arthur! For us, automating this is entirely about OEMConfig. We manage a large fleet of rugged devices and use the Knox Service Plugin (KSP) and Zebra OEMConfig to push advanced granular policies that native Android Enterprise doesn’t cover. 

The main issue with OEMConfig apps is that they apply silently in the background. If a specific policy fails to apply (maybe due to an OS version mismatch or a typo in the JSON payload), the app doesn’t crash on the user’s screen, and they have no idea anything is wrong. By scheduling an automated App Feedback request to run weekly, we proactively pull those configuration states and error logs directly into the Hexnode dashboard. We catch non-compliant devices and silent errors before they become a security risk, rather than waiting for a user ticket. 

Adding to what @carter said, it’s also brilliant for managing custom Enterprise Apps. 

Our in-house dev team built a custom inventory scanner app for our warehouse workers. We specifically built it to support the Android Managed Configurations feedback channel. By setting up an automation in Hexnode to request feedback daily at midnight, our developers get a fresh influx of diagnostic logs, warning states, and success metrics right in the UEM console every morning. 

We no longer have to track down a warehouse worker and ask them to plug their device into a PC for ADB debugging. It basically turns Hexnode into an automated crash-reporting and health-monitoring tool for our proprietary software. 

Essentially, automating the feedback request takes the manual chore out of log retrieval and ensures your compliance and health metrics are never stale.