Guide
Validation and Offline Troubleshooting
Separate a transport problem from a confirmed invalid access decision.
SoundSync
Validate the reason for offline access
| Observation | Action |
|---|---|
| No previous authorization | Connect and activate/validate. A cold installation cannot grant itself grace. |
| Valid signed JUCE grant with outage | Use only its verified product/device-bound expiry. The period starts at the last successful online check, not the first failed request. |
| offline_lease_expired / disabled grace | Reconnect. Restarting or editing cached dates cannot extend the grant. |
| clock_anomaly | Correct the clock and reconnect; do not suppress the check. |
| Confirmed refunded/revoked/expired access | Keep locked and resolve the purchase/support issue. |
| deactivation_pending | Offline grace is not offline device release. Keep locked and reconnect to confirm server deactivation. |
Use the package you shipped
An Access policy change reaches an already capable client after successful online validation. New package source or public keys require rebuilding and distributing the plugin. HISEScript and native HISE have their own enforcement paths.
SoundSync
Detailed offline checks
Use the recovery for the package you ship
For JUCE, a saved date is not enough: the grant must pass signature, product, activation, device and expiry checks. Reconnect and validate an expired or older unsigned cache. Missing public keys require the matching regenerated package and rebuilt plugin; they cannot be repaired by editing local state.
Use the JUCE troubleshooting matrix for clock_anomaly, offline_lease_expired, secure-storage failures and deactivation_pending. Confirmed entitlement or refund denials need their own account/support recovery, not a renewed offline period.
SoundSync