Activate Debug Logs
Enable SDK for troubleshooting and profiling
In some cases, in order to identify the source of an issue, we require Geofence SDK logs from your app. These logs are used for reporting events from our SDK which are useful when debugging and troubleshooting how our code is behaving in your app. Logs must be enabled within your App Code as part of SDK implementation. For this reason, we recommend using a non-production app to troubleshoot
Activate Logs
Find the Implementation details for enabling logging required by support below.
In SDK, the log level defaults to warn but you can easily change it by setting logLevel property of SDK
WoosmapGeofenceManager.shared.logLevel = .info
Different Log Levels
* No log messages.
.none = 0,
* Log error messages.
* Used for critical errors, parse exceptions and other situations that cannot be gracefully handled.
.error = 1,
* Log warning messages.
* Used for API deprecations, invalid setup and other potentially problematic situations.
.warn = 2,
* Log informative messages.
* Used for reporting general SDK status.
.info = 3,
* Log debugging messages.
* Used for reporting general SDK status with more detailed information.
.debug = 4,
* Log detailed tracing messages.
* Used for reporting highly detailed SDK status that can be useful when debugging and troubleshooting.
.trace = 5
Was this article helpful?
Have more questions? Submit a request
