Troubleshooting & Security

1. Security & Diagnostics (Brief)

Use debugMode: false and showDebugScreen: false in production builds.
Optional: use KLP.shared.isDeviceSecure() or performSecurityChecks() to check device status.
When debugMode: true, printDebugInfo() can output detailed console logs (development only).

2. Common Errors

Condition	Possible Cause
`notInitialized`	`initialize` was not called, or security checks failed.
`securityChecksFailed`	Jailbreak, debugger, simulator (production profile), or other security rules. Temporarily use `debugMode: true` during development.
`logEvent` has no effect	`setUser` was not called or user ID is missing.

3. Version

You can read the embedded SDK version using the KLP.version constant.

For questions, please contact the project owner or the KLP integration team. This file covers SDK usage only; architecture and internal implementation notes may be kept in other documents at the repository root.