Troubleshoot login, entitlement synchronization and offline licensing

HTTP testing on customer servers and private networks

English · Deutsch · Italiano · 简体中文 · 繁體中文 · हिन्दी · Español · العربية · Français · বাংলা · Português · Bahasa Indonesia · اردو · 日本語

Returned status	How the application should respond
`EMAIL_VERIFICATION_REQUIRED`	Ask the customer to verify their store email, then retry sign-in.
`ENTITLEMENT_PENDING`	Show synchronization in progress and follow the SDK bounded retries. Check payment, entitlement and licensing jobs in administration.
`ENTITLEMENT_NOT_PURCHASED`	Offer the relevant purchase or let the customer switch to the store account that owns it.
`ENTITLEMENT_EXPIRED` / `ENTITLEMENT_SUSPENDED`	Block protected operations and offer renewal or merchant support.
Network interruption or device limit reached	Use only an offline grant verified by the SDK that is still valid. For device limits, guide the customer through explicit device release.

Sessions are memory-only by default. Remembered sign-in requires the language package secure store or an OS credential vault. Explicit 401/403/404 responses, account mismatches, cancellation and rate limits must never become offline success.