> For the complete documentation index, see [llms.txt](https://docs.blynk.io/en/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.blynk.io/en/legacy-platform/legacy-articles/app-and-board-logs.-how-to-send-application-and-board-logs-correctly.md).
# App and board logs. How to send application and board logs correctly
{% hint style="warning" %}
This documentation is for the LEGACY version of Blynk platform which is no longer supported and will be shut down.
You can sign up for the current version of Blynk platform [here](http://blynk.cloud/dashboard/register).
The new mobile apps can be downloaded from [App Store](https://apps.apple.com/us/app/blynk-iot/id1559317868) and [Google Play](https://play.google.com/store/apps/details?id=cloud.blynk\&hl=en\&gl=US).
The actual Blynk documentation is [here](https://docs.blynk.io/).
{% endhint %}
### How to prepare and send the logs?
#### Mobile app \[Android and iOS]
Please follow these steps:\
1\. Open your standalone application\
2\. Log into your account\
3\. Open device section:
4\. Click the version button:
5\. Click "Clear logs" button":
6\. Reproduce the issue again\
7\. Click "Send logs to developer" button:
8\. Choose your Email client \[Gmail, Spark, etc.]\
9\. Add [**issue name**](https://app.intercom.com/a/apps/hhaxrs9k/articles/articles/4558850/show) to the email body
10\. Click "Send" button\
\
In case you have issues logging into the application or connecting to a server you can send logs from the app splash screen. To do this, you need to long click on the logo:
#### Hardware
Please follow these steps:\
1\. [Activate](https://docs.blynk.cc/#troubleshooting-enable-debug) the detailed logging \[debug mode]\
2\. Flash the new sketch to your board\
3\. Open Serial Monitor Output:
4\. Reproduce the issue:
5\. Save board logs as a separate text file\
6\. Attach the file to email with [**issue name**](https://app.intercom.com/a/apps/hhaxrs9k/articles/articles/4558850/show) and description of the issue
#### **Bare-minimum sketch**
If an issue is in your code and it is not reproducible with the Sketch Template please send us a bare-minimum sketch. It allows you to reproduce the issue and does not contain unnecessary logic because we will not be able to review all your lines of code.
#### **Other**
If your issue is with:\
1\. UI / UX: we will need a screenshot with the issue
2\. Communication with a server: we will need your application logs\
3\. Sending data between board-server-application: we will need your application logs / Serial Monitor Output / bare-minimum sketch\
4\. If a screenshot will not display the issue because it is not static or it is difficult to describe it with the text - we will need a video.
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.blynk.io/en/legacy-platform/legacy-articles/app-and-board-logs.-how-to-send-application-and-board-logs-correctly.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.