Skip to main content

​
1. Quick‑Start Update Checklist

Step Action Notes 1 Publish new APK/IPA to Resources › Native Apps › Internal Use Edit › Upload in the existing app entry. 2 Push to target Smart Groups with Save & Assign Keep the same groups & push mode (Auto / On Demand). 3 Verify permissions Device Admin, Overlay, and Accessibility persist automatically. 4 Restart the device Mandatory – reloads kiosk bindings & clears stale caches. 5 User re‑signs into Workspace ONE Launcher Restores normal operation with updated app version. Why restart?
  • Reloads Lock Task Mode with the new package signature.
  • Ensures Workspace ONE SDK re‑attests the updated binary.
  • Flushes obsolete shared libraries that can cause crashes.

​
2. Troubleshooting Matrix

Symptom Root Cause Fix App not recognized as trusted SDK profile missing or removed Assign (or re‑assign) an SDK profile → Save & Publish. App not installing / icon missing • Wrong Smart Group• Launcher layout not updated• Push mode set to On Demand
  1. Check group assignment.2) Ensure icon is in launcher layout and republish.3) Switch to Auto or push manually from console.
App not functioning after update • New APK signed with a different key• Device not restarted
  1. Re‑sign APK with original certificate.2) Reboot device, then re‑login to Launcher.
Stuck on permission request screen Required permissions not fully granted while in admin mode While the prompt is displayed:1) Tap in‑app shortcuts to Settings.2) Enable Device Admin, Display over other apps, Accessibility.3) Relaunch app. Permissions screen keeps reappearing One or more permissions toggled off later Manually verify each permission in Android Settings; enable any that are off. Lock Task Mode not working • App not in Allowlisted Apps• System buttons allowed Add package name to allowlist; disable Home & Global Actions if kiosk behaviour is required. Reboot if device boots into pinned mode. App crashes / unexpected behaviour • Conflicting UEM device policies• OS‑specific issue
  1. Collect device logs (adb logcat or console logs).2) Test on alternate OS versions/hardware.3) Review other profiles for policy conflicts.
🛠 Still stuck? Email support@oloid.com with:
  • Console deployment logs (Apps & Books › Internal Apps › More › View Logs)
  • Device model & Android version
  • App version code
  • Screenshots or crash logs
Providing these details helps us resolve your issue faster.

​
3. Best‑Practice Tips

  1. Stage roll‑outs – pilot with a small Smart Group before fleet‑wide deployment.
  2. Automate reboots – use the UEM Reboot command to guarantee compliance.
  3. Keep a rollback APK – retain the last working build in case immediate downgrade is needed.
  4. Document change history – track version numbers, push dates, and issues observed for auditability.
Document version: July 28 2025