GA360 Workstation: Application installation and maintenance

Application installation and maintenance

Install/Update downloads the correct app release from the connected Hub and uses its known managed destination, normally ~/.local/share/gameaction360-APP-NAME. Manual ZIP is a separate option and accepts an app ZIP or complete Hub ZIP. Both require entitlement and administrator access. Native dependency installation may request the Linux administrator password in a terminal. Card feedback reports downloads, verification, installer phases and completion/failure; active worker progress can recover after Workstation restarts.

End active work and Close app before maintenance. One maintenance operation runs at a time; assigned apps cannot reopen during maintenance. Archive identity, version, size, SHA-256, file hashes and safe paths are checked. Same/older releases are refused. Per-app updaters retain declared settings and support code rollback; dependency changes may require a full installer. Runtime environments, recordings and saved configuration remain.

Uninstall is administrator-only for closed apps. Installed apps allows removal after an entitlement expires. Removal deletes package-owned code and matching launchers and clears only a matching kiosk assignment. It retains customer data, modified/extra files and dependencies. Reinstall uses the normal entitled installation flow. External OS shortcuts or older copies retain their own app authentication and behavior.

PIN/assignment: ~/.ga360-workstation/station.json. Install staging/logs: ~/.ga360-workstation/installations/. Custom installed paths may be supplied through --config PATH.json. Initial setup requires an 8–32 digit PIN with no default. Use python3 install.py --change-pin with the current PIN to change it.