Guide
Before You Begin
Prepare the product, integration, and test identities before implementing licensing.
SoundSync
Prepare the integration
-
Save the product
Configure the intended license mode, activation mode, device allowance, price, and delivery.
-
Choose a package
Use HISEScript, native HISE, JUCE, or your own HTTP runtime; do not mix their include/build instructions.
-
Match the credentials
Use the generated contract for that product and environment. Native public identity is different from the standard key/secret path.
-
Prepare test identities
Use permitted test customers, owned and unowned products, and distinct devices. Never use another customer's serial to test a claim.
-
Plan enforcement
Determine which audio and features remain locked before valid access. An activation overlay alone is not audio enforcement.
-
Plan diagnostics
Log operation and safe error codes, not passwords, serials, tokens, or customer details.
Use the right success criterion
Credential verification, customer sign-in, entitlement, device activation, and audio unlock are different checks. Test each instead of treating one successful request as proof of the entire integration.
JUCE 0.9.3 supports signed offline access. In the bounded grace mode, successful online activation or validation applies the period selected in product Access settings, up to 90 days and capped by any earlier entitlement or subscription deadline. Zero, disabled, missing or expired grace requires online authorization in that mode. An explicitly authorized permanent-device purchase is different: its signed product/content grant can have no recurring offline deadline. Never infer permanent access from a cached date, a catalog response or an unsigned success flag. Confirmed denial and local deactivation lock access.
