Guide
Device Limits and Deactivation
Control active device use without confusing it with a refund or ownership transfer.
Use stable device identity
The integration submits the machine identity used by its generated contract. Keep it stable across ordinary restarts. Randomizing it on every launch can consume device allowance and produce confusing activation history.
Activation checks the product allowance and existing device use. A limit rejection is not a network outage. Show the customer the supported deactivation/support path rather than silently inventing another identity.
SoundSync
Resolve a full allowance
-
Inspect active devices
Use the permitted customer library or developer customer context.
-
Deactivate the intended device
Release only the selected activation through the supported action.
-
Activate again
Use the current customer proof and stable machine identity.
-
Revalidate access
Check the exported product and the former device state under the package policy.
Different actions, different consequences
Resetting activations, suspending product access, removing an entitlement, and refunding an order are not interchangeable. Review the specific customer/product before taking an administrative action.
Package-specific access policy
JUCE 0.6.0 requires online renewal at startup. Valid saved credentials are reused without repeated sign-in, but offline audio access is unavailable in this release. HISEScript offline grace is a different package policy.