Debugging & Logs
CiaoSDK offers four log levels. Set the log level from Ciao Games → Settings.
Log Levels
| Level | Description |
|---|---|
| Info | All logs including diagnostics. Use during integration and testing. |
| Warning | Warnings and errors only. |
| Error | Errors only. |
| None | No CiaoSDK logs. |
Production Recommendation
Use Info only during integration and testing. Set to Warning or lower for production builds.
Vendor SDK Log Mapping
CiaoSDK's log level also controls verbosity of the underlying vendor SDKs where possible:
| CiaoSDK Log Level | Singular native logs | LevelPlay adapter debug | ByteBrew |
|---|---|---|---|
| Info | Enabled | Enabled | Not controllable |
| Warning | Disabled | Disabled | Not controllable |
| Error | Disabled | Disabled | Not controllable |
| None | Disabled | Disabled | Not controllable |
Singular: native logs are gated to
Infoonly to avoid exposing the API key in device logs on production builds.LevelPlay: adapter debug output (e.g. AdMob, AppLovin, Pangle) is silenced below
Infoto reduce noise in production logs.ByteBrew: the Unity SDK does not expose a log control API. ByteBrew's own logging is not affected by CiaoSDK's log level.
Updated about 1 month ago
Did this page help you?
