What Problem Does This Solve?
Before you can use the LCK SDK, you need to initialize it withLckCore.Initialize(). This process can fail for several reasons: missing tracking ID, invalid arguments, network issues, or user not logged in.
CoreError provides specific error codes for these initialization and core-level failures so you can diagnose and fix setup problems.
When to Use This
You’ll encounterCoreError when:
- Initializing the SDK with
LckCore.Initialize() - Operations require authentication (user login)
- Passing invalid arguments to core methods
- SDK encounters internal errors during setup
LckError).
Quick Example
Error Breakdown
MissingTrackingId
When it happens: You passednull, empty string, or invalid tracking ID to Initialize()
How to fix:
https://dashboard.liv.tv/dev/
InvalidArgument
When it happens: You passed invalid data to a core method (bad GameInfo, null parameters, etc.) How to fix:UserNotLoggedIn
When it happens: Operation requires authentication but user hasn’t logged in How to fix:InternalError
When it happens: Unexpected SDK internal failure What to do:- Check the full error message:
result.Message - Look for more details in Unity console or device logs
- Report to LIV support with:
- Error message
- SDK version
- Platform (Android, Windows, etc.)
- Steps to reproduce
Complete Error Reference
Common Initialization Pattern
Best Practices
Validate inputs — Check tracking ID and GameInfo before initializing
Initialize early — Call in
Awake() or Start() before using SDKHandle all errors — Don’t ignore initialization failures
Log details — Include platform, SDK version in error reports
Don’t ignore initialization errors
Debugging Tips
Check if already initialized
Validate tracking ID format
Test with mock data
Related
- GameInfo — Required initialization parameter
- LckError — Runtime operation errors
- Initialization Guide — Complete setup walkthrough