Simplifier Mobile Client Logs

Created by Daniel Bieberstein, Modified on Fri, 10 Mar 2023 at 05:05 PM by Daniel Bieberstein

For detailed error reporting within our mobile client , it is necessary to produce and send qualified logs to your Simplifier Key User in your organization. In case of an error , please setup the following steps

Step 1 – Open the Settings View


The necessary settings for error reporting can be found on Android and iOS under Settings → Error Handling.

Android Client

iOS Client

Step 2 – Set Native Log Level to Verbose (for Android Devices only)

The Log Level Settings sets  which type of logs are saved – by default only “errors” are saved. For the most accurate logs and best for error analysis, the value “Verbose” is best.

Step 3 – Reproduce the Error

To ensure that the Logs contain all the relevant and qualified information, you should now reproduce the error again.


Step 4 – Send the error to your Key User Support

The error description must be filled out and the privacy policy must be accepted for this option to become active. A click on the button opens the default email client of the device. If several options are displayed, please use the configured email client.

If a ticket already exists to which this log should be sent, the subject of the email must be changed to the following scheme:

“[Ticket#TicketNumber] Free text”

Example: “[Ticket#202010019500022] Android client crash”.

The recipient must be specified as “support@simplifier.io”.

The email including the attachment will be attached to the ticket and can be viewed by all participants in our support portal.

Step 5 – Sync the log back to the Simplifier Server (optional)

Sends the collected Logs to the registered Simplifier Backend and can be found under in the category “Mobile”.

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select atleast one of the reasons

Feedback sent

We appreciate your effort and will try to fix the article