> For the complete documentation index, see [llms.txt](https://docs.secure-contacts.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.secure-contacts.com/how-to/how-to-share-logs.md).

# How to - Share Logs

When troubleshooting an issue with Secure Contacts App (SCA), support may ask you to provide application logs. Follow the steps below to reproduce the issue and share the logs with the SCA support team.

{% hint style="info" %}
The following steps apply to the mobile version of Secure Contacts App (SCA).
{% endhint %}

## Before you start

Make sure that:

* You have access to the email account you want to use for sharing the logs.
* You know which action caused the issue.
* You can describe what you expected to happen and what happened instead.

## Steps

{% stepper %}
{% step %}

### Completely close SCA

* Open the mobile device's app switcher and terminate Secure Contacts App \
  by swiping it away.
  {% endstep %}

{% step %}

### Re-open SCA

* Start Secure Contacts App again and sign in if required.
  {% endstep %}

{% step %}

### Synchronize your contacts

* In SCA, start a manual contact synchronization and wait until the synchronization has finished or the issue occurs.
  {% endstep %}

{% step %}

### Enable logging

* Open the app menu and go to:

**More** → **Settings**

Enable **Logs**.<br>
{% endstep %}

{% step %}

### Open the logs

* Return to the app menu and select:

**More** → **Logs**
{% endstep %}

{% step %}

### Share the logs

* Tap the **Share** button and send the exported logs by email to:

{% hint style="info" icon="envelope-open" %}
**<pvs-support@provectus.de>**
{% endhint %}

\
Send the email after reproducing the issue so that the logs contain the latest information.
{% endstep %}
{% endstepper %}

## Information to include in the email

Please provide the following information in your email:<br>

1. What happened, when did it happen, and what did you expect instead?
2. Can the issue be reproduced, and what steps cause it?
3. Does the issue also occur for other users or on another mobile device?

{% hint style="warning" %}
Do not include passwords or other confidential information in the email.
{% endhint %}

## Optional: Example email

If helpful, you can use the following template. Complete the information and attach the exported SCA logs before sending the email to <pvs-support@provectus.de>.

```
To: pvs-support@provectus.de
Subject: SCA logs – [short description of the issue]

Hello SCA Support,

I am experiencing the following issue in Secure Contacts App:

1. What happened, when did it happen, and what did you expect instead?
   [your answer]
2. Can the issue be reproduced, and what steps cause it?
   [your answer]
3. Does the issue also occur for other users or on another mobile device?
   [your answer]

The exported SCA logs are attached.

Kind regards,

[Your name]
```


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.secure-contacts.com/how-to/how-to-share-logs.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.