NewPipe/.github/ISSUE_TEMPLATE/bug_report.md

---
name: Bug report
about: Create a bug report to help us improve
labels: bug
assignees: ''

---

<!--
Oh no, a bug! It happens. Thanks for reporting an issue with NewPipe. If this is your first bug report, read the following information before proceeding:

Please note, we only support the latest version of NewPipe. In order to check your app version, open the left drawer and click on "About". If you don't have the latest version, upgrade to it and reproduce the problem before opening the issue. The release page (https://github.com/TeamNewPipe/NewPipe/releases/latest) is where you can get it.

P.S.: Our contribution guidelines might be a nice document to read before you fill out the report :) You can find it at https://github.com/TeamNewPipe/NewPipe/blob/HEAD/.github/CONTRIBUTING.md

To make it easier for us to help you please enter detailed information in the template we have provided below. If a section isn't relevant, just delete it, though it would be helpful to still provide as much detail as possible.
-->

<!-- The comments between these brackets won't show up in the submitted issue (as you can see in the preview). -->

### Version
<!-- Which version are you using? Hopefully the latest! We just told you that above! -->
-

### Steps to reproduce the bug
<!--
1. Go to '...'
2. Press on '....'
3. Swipe down to '....'
-->

<!-- If you can't cause the bug to show up again reliably (and hence don't have a proper set of steps to give us), please still try to give as many details as possible on how you think you encountered the bug. -->

### Expected behavior
<!-- Tell us what you expect to happen. -->

### Actual behaviour
<!-- Tell us what happens instead. -->

### Screenshots/Screen recordings
<!-- If applicable, add screenshots or a screen recording to help explain your problem. GitHub supports uploading them directly in the issue text box. If your file is too big for Github to accept, feel free to paste a link from an image/video hoster here instead. -->

### Logs
<!-- If your bug includes a crash (where you're shown the Error Report page with a bunch of info), copy it to the clipboard (there is a share button for this), head over to our bug report to markdown converter at https://teamnewpipe.github.io/CrashReportToMarkdown/ and paste it. Copy the converted text (it is MUCH easier to read this way) from there and paste it here: -->

<!-- That's right, here! -->
Update issue templates 2020-02-23 03:56:56 +00:00			`---`
			`name: Bug report`
			`about: Create a bug report to help us improve`
			`labels: bug`
			`assignees: ''`

			`---`

			`<!--`
Made the bug report template less daunting The biggest problem was that the reporter needed to delete a lot of text to be able to give a clean report. Now most of that is comments. 2020-04-04 11:22:00 +00:00			`Oh no, a bug! It happens. Thanks for reporting an issue with NewPipe. If this is your first bug report, read the following information before proceeding:`
Update issue templates 2020-02-23 03:56:56 +00:00
Made the bug report template less daunting The biggest problem was that the reporter needed to delete a lot of text to be able to give a clean report. Now most of that is comments. 2020-04-04 11:22:00 +00:00			`Please note, we only support the latest version of NewPipe. In order to check your app version, open the left drawer and click on "About". If you don't have the latest version, upgrade to it and reproduce the problem before opening the issue. The release page (https://github.com/TeamNewPipe/NewPipe/releases/latest) is where you can get it.`
Minor improvements 2020-02-24 22:18:48 +00:00
dropping markdown links in comments Co-Authored-By: Tobias Groza <TobiGr@users.noreply.github.com> 2020-03-19 02:42:03 +00:00			`P.S.: Our contribution guidelines might be a nice document to read before you fill out the report :) You can find it at https://github.com/TeamNewPipe/NewPipe/blob/HEAD/.github/CONTRIBUTING.md`
Made the bug report template less daunting The biggest problem was that the reporter needed to delete a lot of text to be able to give a clean report. Now most of that is comments. 2020-04-04 11:22:00 +00:00
			`To make it easier for us to help you please enter detailed information in the template we have provided below. If a section isn't relevant, just delete it, though it would be helpful to still provide as much detail as possible.`
Update issue templates 2020-02-23 03:56:56 +00:00			`-->`
adding version section to bug report 2020-02-28 23:32:14 +00:00
Made the bug report template less daunting The biggest problem was that the reporter needed to delete a lot of text to be able to give a clean report. Now most of that is comments. 2020-04-04 11:22:00 +00:00			`<!-- The comments between these brackets won't show up in the submitted issue (as you can see in the preview). -->`

			`### Version`
			`<!-- Which version are you using? Hopefully the latest! We just told you that above! -->`
			`-`
adding version section to bug report 2020-02-28 23:32:14 +00:00
opus4improvements 2020-03-03 04:52:50 +00:00			`### Steps to reproduce the bug`
Made the bug report template less daunting The biggest problem was that the reporter needed to delete a lot of text to be able to give a clean report. Now most of that is comments. 2020-04-04 11:22:00 +00:00			`<!--`
Update issue templates 2020-02-23 03:56:56 +00:00			`1. Go to '...'`
			`2. Press on '....'`
			`3. Swipe down to '....'`
Made the bug report template less daunting The biggest problem was that the reporter needed to delete a lot of text to be able to give a clean report. Now most of that is comments. 2020-04-04 11:22:00 +00:00			`-->`

			`<!-- If you can't cause the bug to show up again reliably (and hence don't have a proper set of steps to give us), please still try to give as many details as possible on how you think you encountered the bug. -->`
Update issue templates 2020-02-23 03:56:56 +00:00
			`### Expected behavior`
Made the bug report template less daunting The biggest problem was that the reporter needed to delete a lot of text to be able to give a clean report. Now most of that is comments. 2020-04-04 11:22:00 +00:00			`<!-- Tell us what you expect to happen. -->`
Update issue templates 2020-02-23 03:56:56 +00:00
			`### Actual behaviour`
Made the bug report template less daunting The biggest problem was that the reporter needed to delete a lot of text to be able to give a clean report. Now most of that is comments. 2020-04-04 11:22:00 +00:00			`<!-- Tell us what happens instead. -->`
Update issue templates 2020-02-23 03:56:56 +00:00
Made the bug report template less daunting The biggest problem was that the reporter needed to delete a lot of text to be able to give a clean report. Now most of that is comments. 2020-04-04 11:22:00 +00:00			`### Screenshots/Screen recordings`
			`<!-- If applicable, add screenshots or a screen recording to help explain your problem. GitHub supports uploading them directly in the issue text box. If your file is too big for Github to accept, feel free to paste a link from an image/video hoster here instead. -->`
Update issue templates 2020-02-23 03:56:56 +00:00
			`### Logs`
Made the bug report template less daunting The biggest problem was that the reporter needed to delete a lot of text to be able to give a clean report. Now most of that is comments. 2020-04-04 11:22:00 +00:00			`<!-- If your bug includes a crash (where you're shown the Error Report page with a bunch of info), copy it to the clipboard (there is a share button for this), head over to our bug report to markdown converter at https://teamnewpipe.github.io/CrashReportToMarkdown/ and paste it. Copy the converted text (it is MUCH easier to read this way) from there and paste it here: -->`
B0pol suggested improvements 2020-02-24 00:16:18 +00:00
opus4improvements 2020-03-03 04:52:50 +00:00			`<!-- That's right, here! -->`