Skip to content

Troubleshooting

First record the app version, operating system, affected feature area, steps performed, and error message. Before retrying, confirm that you will not create the same batch of tasks twice.

  1. Confirm the app version under Settings → About.
  2. Verify yt-dlp, FFmpeg, and Bun under Settings → Download.
  3. Check the proxy under Settings → Network.
  4. When an account is required, verify sign-in under Library → App Sessions.
  5. Return to the affected page and refresh it or recreate the task.
Symptom Check first
Start is unavailable for a download or transcode For downloads, check yt-dlp and FFmpeg; for transcodes, check FFmpeg.
A link cannot be parsed Check link completeness, account access, yt-dlp, and the network; use Sniffing if needed.
Downloads are slow or frequently fail Lower download concurrency; for HLS or m3u8, also lower segment concurrency.
Transcoding fails Verify FFmpeg and confirm that the input file is accessible and supported.
The sniffing browser does not open Reopen New Sniff to detect browsers again. For Browser Default in Chrome, also check remote debugging and connection permission.
Sniffing finds no resources Click Play, scroll the page, expand the sniffing scope, or reopen the session.
YouTube / Music requests sign-in Verify or reconnect the YouTube App Session.
An online page keeps loading Check the proxy, target service state, and account region.
RSS does not update Refresh the subscription manually and check its source address and the network.
Local music does not play Check whether the file was moved, deleted, or stored on an offline drive.
A Library item is marked missing Remount the drive and check again, or import the existing file again.

Open the log directory under Settings → General. Reproduce the problem once, then find records near that time.

Logs may contain local paths, site addresses, or error context. Remove or hide this information before submission. Do not upload App Sessions, pairing links, tokens, or the complete Library database.

Open GitHub Issues and provide:

  • The XiaDown version and operating-system version.
  • The affected feature area and page.
  • Steps that reproduce the problem consistently.
  • A sanitized error message or log excerpt.
  • Screenshots without accounts, private content, or local paths.