Skip to content

Troubleshooting

This section is the user-facing map for problems in PipePipe. Start from the exact symptom instead of changing several settings at once: each category below collects the information that is actually useful for a diagnosis.

Troubleshooting triage

First steps

  1. Check your installed version against GitHub Releases.
  2. Repeat the problem once and record the time, affected URL or query, and the selected YouTube extraction endpoint.
  3. Open the matching category below. Keep separate symptoms in separate reports.

PipePipe Settings, 5.2.3 on Android 16

Reference capture: PipePipe 5.2.3 · Android 16/API 36. Categories and their order can change between releases.

Categories

Find the right branch quickly

Exact symptomStart hereDo not assume
WebView unavailableWebView and protected playbackThat changing the YouTube endpoint bypasses the WebView check.
AntiBotException, Source error, buffering, live seek failurePlayback, network, and sign-inThat a current WebView or a login proves the cause.
No/incorrect search resultsSearch and discoveryThat a player fix will fix search.
Link opens in the “wrong” playerBackground, popup, fullscreen, and queueThat the preferred-open setting controls in-app taps.
Download fails or a partial file remainsDownloadsThat final SD-card storage is the only storage used.
Lost local data after migrationSetup, updates, and backupsThat an import behaves as a reversible merge.
App/UI/locale/device-specific issueApp and deviceThat it is automatically a YouTube extractor fault.

Setup and reporting

YouTube and playback

Library and content controls

App and device

One symptom, one report

WebView, stream playback, and search can fail at the same time after an upstream YouTube change. They still take different code paths. Separating them gives the maintainer a usable reproduction instead of one ambiguous report.