Move Players Off an Affected App Build: A Guide to Cloud Rollback for Tizen, BrightSign, LG webOS, and Qbic
Appspace maintains a centralized, cloud-managed rollback for purpose-built media players, including Samsung Tizen (SSSP), BrightSign, LG webOS, and Qbic devices. When an application release shows unexpected behavior or instability, Appspace moves connected players off that build and onto a verified stable release, without anyone going on site. Cloud rollback means moving devices off an affected build onto a stable build. That target is not necessarily a downgrade. It may be a newer hotfix or an older previously verified release, depending on what Appspace publishes as the stable release.
This guide is for administrators who manage those players. Connected players on Latest and players pinned to the affected build both leave that build over the network. A reboot can apply the stable package before the next scheduled update window. BrightSign players on Appspace App v2.92 or later can also recover on the device when a launch keeps failing. A player that is completely offline stays on its current build until you apply the stable package locally.
Key Benefits
- No site visit for connected players — Version redirection runs through the Appspace update service. Connected devices move to the stable build over the network, including Qbic devices once Appspace publishes a newer stable build for them.
- Latest and pinned devices both move — A device that follows Latest and a device pinned to the affected version are redirected to the latest verified stable release for that platform.
- Sooner than the maintenance window — Reboot an affected device, through remote management or a power cycle, to check in before the next scheduled update window.
- A stable build each platform can install — BrightSign, Tizen, and LG webOS can install an older package when that is the stable build. Qbic cannot install a lower version, so Appspace publishes a newer stable build when a rollback is needed.
- BrightSign can recover on the device — On Appspace App v2.92 or later, a BrightSign player that boot-loops after launch restores its previous package, then tries a cloud download, then waits and retries.
What This Guide Covers
- How Appspace marks a build as affected and redirects devices
- Scheduled update windows, and rebooting to check in sooner
- The BrightSign 15-minute cool-off between boot update checks
- Which platforms use cloud rollback, and which use local recovery
- BrightSign boot-loop recovery and the order it tries
- Manual recovery when a player is completely offline
Prerequisites
- The player is a BrightSign, Samsung Tizen (SSSP), LG webOS, or Qbic device. Cloud rollback applies to these platforms.
- The player can reach the Appspace update service. A player that is completely offline cannot receive the cloud redirect.
- For BrightSign on-device boot-loop recovery, the player is running Appspace App v2.92 or later. Samsung Tizen, LG webOS, and Qbic do not use this local backup recovery.
- To pull the stable package before the next scheduled window, you can reboot the device through remote management or a power cycle.
- To recover a player that cannot reach the network, you have the stable application package and can apply it through storage, an SD card, or the local device interface.
Steps
1. Appspace marks the build as affected
When an issue is identified with a specific app build, Appspace updates its cloud release configuration and marks that build as affected for the relevant device platform or platforms (Samsung Tizen, BrightSign, LG webOS, or Qbic).
2. Connected devices are redirected to the stable release
The Appspace update service checks each device's update request against Appspace's cloud release configuration. Any device requesting the affected build is redirected to the latest verified stable release available for that platform.
This includes both of these devices:
- A device configured to follow Latest
- A device pinned to that specific affected version
The target is the stable build Appspace publishes. It may be a newer hotfix or an older previously verified release.
3. Wait for the scheduled update window
Devices with standard update schedules, for example daily off-peak windows, detect the change on their next scheduled check-in. They download the stable package and move to that build automatically.
4. Reboot to check in sooner
Devices also check for their target version when they boot. Reboot affected devices through remote management or a power cycle to force an earlier check-in.
On BrightSign, boot-time update checks run at most once every 15 minutes. A reboot shortly after a recent update check does not contact the Appspace update service again until that cool-off has elapsed. When you need an immediate cloud pull, wait at least 15 minutes since the last check, then reboot. Otherwise, leave the device for its next scheduled update window.
5. Match the stable build to the platform
BrightSign, Tizen, and LG webOS can install an older package when that is the stable build.
Qbic does not support installing a lower version, so it cannot move to an older stable build. For Qbic, Appspace publishes a newer stable build when a rollback is needed. Qbic devices can then move off the affected build.
| Mechanism | Platforms |
|---|---|
| Cloud rollback | BrightSign, Samsung Tizen, LG webOS, Qbic |
| On-device boot-loop / local backup recovery | BrightSign only (Appspace App v2.92+) |
Samsung Tizen, LG webOS, and Qbic rely on the cloud path. They do not use BrightSign's local backup self-heal.
6. Let BrightSign local recovery run
On BrightSign players running Appspace App v2.92 or later, an on-device safeguard monitors stability after launch. You do not start this recovery. The player starts it.
Local rollback runs when the player detects repeated reboots within a short period after launch. The player treats that pattern as a crash / reboot loop.
Local rollback may also run after:
- App initialization failure
- App initialization timeout
- Broken or incomplete package extraction
When local rollback runs, the player tries recovery in this order:
- Restore from local backup — the previous working application package on the device.
- Cloud download — if the local backup is missing or incomplete, download the redirected stable package from the network.
- Self-recovery wait — if both fail (the player is offline, there is no valid backup, or the update check was skipped by cool-off), the player shows an on-screen recovery message for 15 minutes, then reboots and retries.
7. Recover a player that is completely offline
A player that is completely offline cannot receive the cloud redirect. It stays on its current build until it reconnects.
Apply the stable application package through storage, an SD card, or the local device interface.
On BrightSign, if local recovery cannot complete (no valid local backup and no network), the player shows an on-screen Rollback unavailable message for 15 minutes, then reboots and retries. If it keeps failing, apply the stable package manually the same way.
Use Case
Scenario: A site has BrightSign and Qbic players on a build Appspace has marked affected. One BrightSign has no network.
Connected players download the stable package at the next scheduled check-in. To move a connected BrightSign sooner, wait at least 15 minutes after its last update check, then reboot it through remote management or a power cycle. The Qbic players move after Appspace publishes a newer stable build, because Qbic cannot install a lower version. The offline BrightSign stays on the affected build until you apply the stable package from storage or an SD card. If that BrightSign is on Appspace App v2.92 or later and reboots repeatedly shortly after launch, it tries its local backup, then a cloud download, then shows a recovery message for 15 minutes and retries.
Quick Reference
| Topic | Detail |
|---|---|
| Cloud trigger | Appspace marks the build as affected in its cloud release configuration for the affected platform or platforms |
| Devices on Latest or pinned | Redirected away from the affected build |
| Rollback is not always a downgrade | Target is the stable build (newer or older) |
| BrightSign cloud cool-off | 15 minutes between boot update checks |
| BrightSign boot-loop trigger | Repeated reboots within a short period after launch |
| BrightSign local fallback | Backup, then cloud download, then a 15-minute message and reboot |
| Platforms with cloud path | BrightSign, Samsung Tizen, LG webOS, Qbic |
| Platforms with local self-heal | BrightSign only (v2.92+) |
Troubleshoot
| Symptom | Likely cause | What to try |
|---|---|---|
| A connected player is still on the affected build | It has not reached its next scheduled check-in | Wait for the scheduled update window, or reboot to force a check-in. |
| A BrightSign reboot did not pull a new package | Boot-time update checks run at most once every 15 minutes | Wait at least 15 minutes since the last check, then reboot. Or wait for the next scheduled update window. |
| A Qbic player cannot move to the stable build you expected | Qbic does not support installing a lower version | Wait until Appspace publishes a newer stable build. Connected Qbic devices then move over the network. |
| A player never leaves the affected build | The player is completely offline, so it cannot receive the cloud redirect | Apply the stable application package through storage, an SD card, or the local device interface. |
| A BrightSign player shows Rollback unavailable | Local backup is missing or incomplete, and the cloud download failed (offline, or the update check was skipped by cool-off) | The player shows the message for 15 minutes, then reboots and retries. If it keeps failing, apply the stable package manually. |
| A BrightSign player on v2.92 or later reboots repeatedly shortly after launch | The on-device safeguard treats repeated reboots within a short period after launch as a crash / reboot loop | Let local recovery run: local backup, then cloud download, then the 15-minute on-screen message and reboot. |

