This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revision | |||
| manual:faq:issue_reporting [2025/12/03 16:03] – [System bug report] mstupka | manual:faq:issue_reporting [2026/07/17 14:24] (current) – mstupka | ||
|---|---|---|---|
| Line 8: | Line 8: | ||
| - **repeat the action leading to the error** at least once more. | - **repeat the action leading to the error** at least once more. | ||
| - | | + | - long-press Locus Map's main menu button to open a hidden tool menu > tap **Report bug** (or " |
| - | - **describe the steps that led to the crash in precise detail** so that we can **replicate the steps you took to reproduce the problem** | + | - a set of logs and a memory dump are generated:\\ {{ : |
| - | | + | - add a description of actions leading |
| - | - a TXT file is generated. | + | - a confirmation dialog appears:\\ {{ : |
| + | - patiently await the support response - this usually doesn' | ||
| - | ===== Locus Map 4.30 and older versions ===== | + | ===== What if the app can't even start? ===== |
| - | + | Sometimes, none of the methods mentioned above help identify the problem (e.g., when the app cannot be started at all), and you are asked by the helpdesk to create a **system bug report**. | |
| - | - do the same as is described above, excluding the " | + | - please |
| - | - open the main menu > helpdesk/ | + | |
| - | + | ||
| - | ===== System bug report | + | |
| - | Sometimes, none of the methods mentioned above helps identify the problem (e.g. when the app cannot be started at all), and you are asked by the helpdesk to create a system bug report. | + | |
| - | - please | + | |
| - **[[how_to_create_debug_log|follow these instructions >> | - **[[how_to_create_debug_log|follow these instructions >> | ||