Bug Reports

Modifying an app is not an easy job, sometimes applying a modification can cause an unexpected bug and we can't catch all of them.

That's where you come in! If you experience a bug and want to help us improve Vanced, you would help a ton by providing a logcat.

A logcat is a log of all processes on your system. This helps a lot with identifying the problem.

BUG REPORTS (all details MUST be included or your report will be ignored):

➼ For all basic reports regarding crashes/force closes of the app, fill all these points below

1. Vanced exact version number (Do NOT say latest).
2. Download link used to download Vanced.
3. Installation method (whether used SAI or Vanced Manager)
4. Device.
5. ROM (optional may not help).
6. Any applied Substratum/swift overlays.
7. Logs if there are any crashes/force closes (upload to Pastebin or hastebin or katbin) and paste the link of it with your report. [Check here to know how to get logs]
8. A brief description of the issue
9. Any installed mods to the system.
10. Test your issue on the stock youtube app

{The link to download the Official YouTube app can be found here} Install it with SAI app.

The current version for Vanced is 17.03.38 hence you are requested to check the issue with official YouTube app. If the issue persist there, there's nothing we can do. Wait for Google to fix it. Else provide the bug report as asked.

⚠️⚠️⚠️If you don’t include the 10th detail your report will be ignored.⚠️⚠️⚠️

➼ If your bug is not related to installation/crashing issues but related to UI/UX, features, then you can report your bug on our GitHub repo using the link below. or you can head to our discord server.

The link can be found below for both:

• GitHub Repo(Click me)
• Discord Server(Click me)

Be sure to follow the rules of the Discord chat, and follow #feedback-guide if you want your bug report to be noticed and documented.

How to get logs

Wondering how to take logcats/crash logs and too lazy to search google, there are three methods you can use to get them.

Method 1:- Needs a pc/laptop with adb installed.

⦿ ON YOUR PHONE:

1. Open your settings app and go to "About Phone/Phone Info" and click your build number 7 times.
2. Now go back to the settings main menu.
3. You will now either have a new tab Developer Options in this menu or in the system menu.
4. Open Developer Options and enable USB-Debugging.

⦿ ON YOUR PC/LAPTOP:

1. Visit this website and download the tools for your operating system.
2. Extract them.
3. Open the extracted folder to find many .exe files.
4. Shift + Right-click the background of the extracted folder and select. Then Run command prompt / PowerShell here.
5. Plug your phone into your PC with USB-Debugging Permission toggle on and grant it from your phone.
6. Type "adb devices". If your phone is shown, proceed. If not, google for [your BrandHere] USB drivers and install them. Then check if the device shows or not and proceed further.
7. Type adb logcat > logcat.txt".
8. Open your Vanced app, reproduce your bug and then close the command prompt.
9. Now you will find a new file logcat.txt in the same folder.
10. Open it, scan it quickly to remove confidential info.Press "CTRL + A" => "CTRL + C", open https://hastebin.com/ or https://pastebin.com/ , paste it and save. Use the output link for your bug report.

Method 2:- Using logcat reader apps(Need root)

Use any logcat reader app from the Google Play store to capture the error, save the text file, and share it with your developer/moderator, or paste the error text into dogbin or Pastebin and share the link with them. We recommend using any one of the alternatives:

• Matlog
• Catlog
• Logcat Reader

Method 3:- Either adb or root permission is required

The scoop app can help get logs of the app which is getting crashed unexpectedly so you don't need to go through the hassle of doing logcats and getting a big stack trace of logs.

1. Download and install the scoop app.
2. Grant root permission or grant via pc through adb using this command "adb shell pm grant taco.scoop android.permission.READ_LOGS" without apostrophes.
3. Then keep the scoop app in the background and reproduce the crash
4. Upload/Copy the stack trace to katbin/Pastebin
5. Paste the link of the crash log in the chat.

(The scoop app link can be found using this link)

NOTE: If you don't have adb installed on your laptop/pc, use this link to download ADB on your PC/macOS/Linux by following the instructions properly.