Notable Feature

This version expanded logging capabilities. Host app can now receive also information about log level. This for example can be used to log and non-fatal SDK errors.

Secondly logs can now be collected and uploaded only after manual trigger. This can be used to support users' having specific, hard to identify issues.

Warning: Be aware that uploading SDK log information exposes to specified server users sensitive information, such as, but not limited to

  • users' current location and part of location history
  • users' search term including offline searches and navigation
  • users' interactions with map

This is samle configuration for log appenders to enable ad-hoc log collecting.
(configuration you're using may differ, please create developer support ticket if you have any questions)

"Logging": [
    {
      "name": "global",
      "classpath": "",
      "appenders": [
        {
          "class": "CConsoleAppender",
          "level": "debug",
        },
        {
          "class": "CFileAppender",
          "level": "debug",
          "file": "global.log",
        },
        {
          "class": "TelemetryAppender",
          "level": "ProcedureCall",
          "url": "[address-provided-on-request]",
          "username": "[login-provided-on-request]",
          "password": "[password-provided-on-request]",
         "auto_send": false
        },
        {
          "class": "DiagnosticsAppender",
          "level": "ProcedureCall"
        }
      ]
    }
  ]

Note: Be sure to set Logging.appenders.auto_send to false for TelemetryAppender.
If not set properly all of the log data will be uploaded to configured server resulting in increase of users' data consumption and load on specified server.
In case you're using our logging server, this will result in rejection of your login and thus disabling all log collection to prevent disruption of our service.

To manually trigger log upload use

// iOS:
SYLogConnector.sendTelemetryLog

//Android:
LogConnector.SendTelemetryLog