Troubleshooting
Use this list for common integration checks for SDK v1.0.0 (beta). For product-specific behavior, tiering, or config issues, contact AdScope support with your package version (1.0.0) and platform.
Empty key-value string
| Check | Action |
|---|---|
| First launch / no events yet | Confirm you’ve reported ads (or applied initial values) per AdScope guidance before expecting a key-value. |
| Config not applied | Ensure FetchConfigurationAsync succeeded or SetConfigFromJson ran with valid payloads from AdScope. |
| Per-format API | If you use GetKeyValueForFormat, ensure that format has been reported as your flow requires. |
Configuration not updating
- Confirm you refresh configuration when AdScope says to (launch, resume, interval, etc.).
- Check network, credentials, and environment (staging vs production) per your integration guide.
Different behavior in Editor vs device
- Compare network access, certificates, and API keys between Editor and device builds.
- Follow AdScope’s guidance for testing configuration.
Still stuck?
- Confirm Unity and package versions meet AdScope requirements.
- Open a ticket with AdScope; avoid sharing secrets or full config in public channels.