SkieWhat happens if a Skie update goes wrong, and is there a rollback?
Staged rollout and the ability to pause a release are the main safeguards: a problem should be found while only a few organisations have the version. The Skie team then pauses the release and ships a corrected build, which devices fetch and verify by checksum. Your rules stay on the devices throughout.
No software team can promise a release will never have a fault, so the useful question is how far a fault can spread and how fast it is contained. Skie's answer is to roll out in stages to chosen organisations. If a problem shows up, the release is paused before it reaches everyone.
A corrected build then follows through the same route. Devices download it automatically, check its checksum and install it. Nobody has to visit the tablets. We do not ask you to repair anything by hand, and the Skie app cannot be stopped or uninstalled by users, so the fix still lands.
Meanwhile your protection continues. Rules are cached and signed on each device, and Android enforces them because Skie is the device owner. The unlock gate keeps devices honest about syncing, and the breach centre will show if devices go quiet as a result of a bad version.
If you suspect an update is causing trouble in your own fleet, note the model, the app version on the device page and what you see, then contact the team. Nightly backups of your configuration exist as well, with restore preview and the ability to restore a previous version, so a settings mistake of your own can be undone separately from app updates.
Practical tip: keep a short log of dates when behaviour changed. It makes diagnosis much faster than a general description.