From 7699d92359e21587b789fdbc057aca931e6b47cf Mon Sep 17 00:00:00 2001 From: Herohtar Date: Thu, 7 Apr 2022 10:29:51 -0500 Subject: [PATCH] Update debug log menu navigation --- Submitting-useful-bug-reports.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Submitting-useful-bug-reports.md b/Submitting-useful-bug-reports.md index 6dbecc4..62305ae 100644 --- a/Submitting-useful-bug-reports.md +++ b/Submitting-useful-bug-reports.md @@ -63,7 +63,7 @@ The developers need to see the bug in order to fix it. Try to find the exact con The debug log describes what Signal was doing while it was running. If you capture a debug log **immediately** after a bug occurs, the developers can use the log to see exactly what was going on in your installation of Signal. Even in the case where you know the exact steps that cause the bug on your device, that doesn't guarantee that the same steps will cause the bug on the developer's device. It is always helpful to add a debug log to your issue report. #### How to capture a debug log -1. Immediately after the bug has happened go to _**Signal Settings -> Advanced -> Submit debug log**_ +1. Immediately after the bug has happened go to _**Signal Settings -> Help -> Debug log**_ 1. Tap **Submit** to generate a URL link for the log 1. Copy the link and paste it in your issue report