Skip to content

更新时间: 6/25/2026

Pixiv BookSource

Troubleshooting

🅿Legado Pixiv BookSource

️ Channel @PixivSource

TIP

Simple Troubleshooting Guide for Legado

NOTE

Please check the following before sending feedback:

  • Legado branch/type (e.g., Sigma, Beta, MD3, etc.)
  • Legado app version (e.g., 3.26.0101)
  • Book source version (e.g., 251)
  • Whether the app version supports the current book source
  • If it is an app issue, please report it to the Legado GitHub repository. Find the link here: Download Legado
  • If it is a book source issue, please submit an issue to the PixivSource GitHub Repository and attach your debug results. See "Debug Book Source" below.

Debug Book Source

🐞 Debug Mode (Optional)

IMPORTANT

⏺ Interactive Menu => Bookshelf - Reading Screen - Pixiv Novel - Login => Debug Mode

️ BookSource Settings => Mine - Source Management - Pixiv Novel - Login => Debug Mode

Turning on Debug Mode (Optional) helps analyze the current issue.

🐞 Debug Book Source

Mine - Source Management - Edit Source - Debug - Enter Content

Debug AreaWhat to Enter
SearchEnter keywords
Discover::https://www.pixiv.net/ajax/top/novel
Detailshttps://www.pixiv.net/novel/show.php?id=123
Content List++https://www.pixiv.net/novel/show.php?id=123
Text Content--https://www.pixiv.net/novel/show.php?id=123
  • It is best to attach the debug info when submitting an error.

Fix Issues

  1. Turn off "Replace & Clean" (替换净化)
  2. Refresh the text content.

Find Issues

🈚️ No Results in Search or Discover

  1. Debug Book Source
  2. Check your network connection
    • Is your network working? Try a different network.
  3. Check and update the Legado app
    • Update the app
    • Try a different version of the app.
  4. Check and update the book source
    • Is the book source imported?
    • Is the book source enabled?
    • Update the book source
  5. Check if the website works
    • Can you open the website used by the booksource?
    • Is the website working normally?
    • Log into the website inside Legado and try again.
  6. Report the issue to the developer