Skip to content

Debug mode and log messages


To aid you in debugging, Plot provides diagnostic messages in the console. These messages are only enabled when Plot is compiled with a debug configuration. The messages show which notifications were considered for showing and how far Plot thinks you are from these notifications. This makes it clearer why a notification has been or hasn't been shown.

XCode's console shows these debugging messages.

Example debug log output

When enabling Plot you see the following log message

2017-09-18 16:34:51.460 - Plot enabled

After the Plot plugin is enabled, it downloads the notifications from the server. It shows the total number of notifications and the notifications that have been loaded. You can use the following message to ensure the right notifications are loaded.

2017-09-18 16:34:54.349 - Loaded new notifications (1 total)
2017-09-18 16:34:54.349 - Notification: a9f242b4be384923896168dc2c134585 - Wiki Notificati...

Once the notifications are loaded, Plot matches these. It shows the loaded notifications and the distance to these notifications in meters. Where the distance is smaller than the match range, a notification "matches" and is sent to the notification filter or geotrigger handler (if you have one or both defined) so that it's processed by the logic that you defined.

2017-09-18 16:34:54.383 - Distance to a9f242b4be384923896168dc2c134585 - Wiki Notificati...: 4018 (range: 200)

When there is at least one notification or geotrigger sent to the notification filter/geotrigger handler, then you see the following line with the number of matching notifications. The example below uses a geotrigger handler. When you don't have a notification filter/geotrigger handler, this step is skipped.

2017-09-18 11:27:25.086 - Offered geotriggers to the geotrigger handler (1 total)

Once notification filter/geotrigger handler completes, then the following log message appears. It shows how many notifications passed through the notification filter and then shows these notifications. These notifications should then appear in the notification area.

2017-09-18 11:27:25.096 - Geotrigger handler completed (1 passed)
2017-09-18 11:27:25.187 - handled: 3fda60abc4fa4472986fb5e108989991;a01a770391134f55be0ce90b88dc13f2 - Plot..

The debug output also includes useful info about:

When the plugin detects a new updates

2017-09-18 17:54:55 - Acquired location: 52.344271,4.916536 (accuracy 65 meter)

Notifications loaded through QuickSync (Integration guide), denoted by the keywords "from push"

2017-09-18 18:00:08 - Loaded new notifications from push (6 total)

Shown notifications

2017-09-18 17:12:48 - Showing notification: da13094b56d0482298d5fba912ad8cbd - Welcome

Sent geotriggers

2017-09-18 17:12:48 - Geotrigger sent: 605ef54c3dd94a3bb87cee0c4d70df98;27d74b87987943d1b93d4dea3ad04081 - test geotrigger...

Region status, e.g "User first has to leave area", which means that to trigger the region the user has to leave and reenter the area, or "Dwell initiated", which means that the dwell timer has started

2017-09-18 17:54:55 - User first has to leave area of 9dee12a6151f4297b366fd82161e1f00;41b1ce9a9f2140ce9512f03b4fafc04b - test