Debugging - SpendOwl

Enable Logging

Turn on debug logging to see SpendOwl activity:

SpendOwl.enableLogging = true

You don’t need to guard this for production — the SDK’s logging is compiled out of release builds entirely. See Where the Logs Go.

Using Build Flags

The #if DEBUG guard is redundant for the SDK’s own output, but it is still worth keeping if you want the line itself gone from release builds:

#if DEBUG
SpendOwl.enableLogging = true
#endif

Log Levels

For more control, use logLevel:

SpendOwl.logLevel = .debug

Level	Description
`.none`	No logging (default)
`.error`	Only errors
`.info`	Errors and important events
`.debug`	All messages including debug info

Example Output

Each line is prefixed with the level it was logged at. Note that the SDK never logs an amount — it does not read prices; see Purchase Tracking.

[SpendOwl] DEBUG SpendOwl SDK v1.4.0 configured (key: spen***c3d4)
[SpendOwl] DEBUG Got attribution token
[SpendOwl] INFO Attribution fetched: attributed
[SpendOwl] DEBUG Purchase tracking started (automatic)
[SpendOwl] INFO External user ID set: user-123...
[SpendOwl] DEBUG Scanning transaction history
[SpendOwl] INFO Recorded transaction: 2000000891234567
[SpendOwl] DEBUG Sent 1 purchase event(s)

Where the Logs Go

SpendOwl logs with print(), so they appear in the Xcode console while your app is running under the debugger — and nowhere else. There is no os_log integration, so Console.app will not show them.

Logging is compiled out of release builds. The logging code is wrapped in #if DEBUG, so a TestFlight or App Store build prints nothing even with enableLogging set to true. Verify your integration from Xcode against a debug build.

This also means there is nothing to turn off before you ship: a release build cannot leak SDK logs, because it does not produce any.

Common Issues

SDK Not Configured

Error: SpendOwl SDK is not configured

Solution: Call configure() before using other SDK methods:

// In App.init() or AppDelegate
SpendOwl.configure(apiKey: "your-api-key")

Invalid API Key

Error: Invalid API key

Solution: Check your API key in the dashboard. Ensure you’re using the correct key for your environment (test vs. live).

Network Errors

Error: Network error: The request timed out

Solutions:

Check internet connectivity
Increase timeout: SpendOwlConfiguration(apiKey: "...", timeoutInterval: 30)
The SDK retries automatically, but persistent failures indicate network issues

Attribution Unavailable

Error: Attribution is not available on this device

Causes:

iOS version below 14.3
AdServices framework not available
Running in simulator (attribution may return mock data)

Solution: Attribution works on iOS 14.3+ on real devices. Simulators may return limited data.

Attribution Denied

Error: Attribution access was denied

Causes:

User or MDM restricted ad tracking
Limited Ad Tracking enabled in Settings

Solution: This is normal for some users. Handle gracefully:

do {
    let attribution = try await SpendOwl.attribution()
} catch SpendOwlError.attributionDenied {
    // User has restricted tracking - continue without attribution
}

Verifying Integration

Use this checklist to verify SpendOwl is working:

Check Configuration

print(SpendOwl.isConfigured) // Should be true

Check SDK Version

print(SpendOwl.sdkVersion) // Should print the installed version

Enable Logging

SpendOwl.enableLogging = true

Trigger Attribution

let attribution = try await SpendOwl.attribution()
print(attribution.status) // Should print a status

Check Dashboard

Visit your SpendOwl Dashboard to see if events appear

Debug Mode in Dashboard

The SpendOwl dashboard shows debug data when using a test API key:

Test events are labeled separately
Don’t affect production ROAS
Useful for verifying integration

Reporting Issues

If you encounter issues not covered here:

Enable .debug logging
Reproduce the issue
Copy the logs
Open an issue on GitHub

Include:

iOS version
SDK version
Relevant logs
Steps to reproduce

Next Steps

Troubleshooting

Common issues and solutions

API Reference

Full SDK API documentation

​Enable Logging

​Using Build Flags

​Log Levels

​Example Output

​Where the Logs Go

​Common Issues

​SDK Not Configured

​Invalid API Key

​Network Errors

​Attribution Unavailable

​Attribution Denied

​Verifying Integration

​Debug Mode in Dashboard

​Reporting Issues

​Next Steps

Troubleshooting

API Reference

Enable Logging

Using Build Flags

Log Levels

Example Output

Where the Logs Go

Common Issues

SDK Not Configured

Invalid API Key

Network Errors

Attribution Unavailable

Attribution Denied

Verifying Integration

Debug Mode in Dashboard

Reporting Issues

Next Steps