[Gourab0002]

Goal

FuckNovelpia chapters keep failing with Cloudflare 403s and following the plugin's advice doesn't help. This makes the fix path work.

Evidence

• Cloudflare only challenges chapter.php. /, updates.php, search.php and /novel/... return 200 with a normal browser UA, while chapter.php?hash=…&ch=0001 returns 403 with cf-mitigated: challenge ("Just a moment...").
• The old message said "Open the plugin in WebView". That opens the site homepage (BrowseSourceScreen navigates with url: site), which isn't challenged, so no cf_clearance cookie is ever set and the retry fails again.
• The reader's error screen WebView button opens chapter.path (ReaderScreen.tsx), which is the challenged URL.
• After that, the retry can pass: RN Android fetch uses ForwardingCookieHandler, which reads WebView's CookieManager, and both fetchApi and WebviewScreen use getUserAgent(). The plugin passes no custom headers, so the app defaults stay in place.

Change

parseChapter failures with 403/503 now tell the reader to tap WebView on the chapter screen, let the chapter load, then retry. List and novel pages keep the old message. Version 1.1.4.

Limitations

This can't stop challenges from coming back. When the clearance cookie expires, or Cloudflare re-checks the reader's network, they'll need to do it again. No headers, proxies or solvers were added.

Checks

• tsc (production), eslint, prettier, npm run build:full: pass
• npm run check:plugin: popular, search and novel pass. Chapter is inconclusive (403 challenge from a cloud host), so the change hasn't been tested on a device.

[greptile-apps]

Confidence Score: 5/5

[Medium impact] The PR appears safe to merge.

Summary

Updates FuckNovelpia’s chapter error guidance and bumps version to 1.1.4.

• Chapter Cloudflare errors point readers to the chapter screen’s WebView.

No actionable issues found. Device recovery was not verified during this review.

_{Reviews (1) · Last reviewed commit: "fix(english/fucknovelpia): send chapter ..." · Reviewed by Greptile}