Got error code 352 - while fetching
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 39k
- Forks
- 2.1k
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 10
Description
Platform
Desktop - Web
Describe the bug
When I try to subscribe any bilibili channel, I get this error:
Error since xx ago.
Got error code 352 - while fetching: 风控校验失败。
ie. https://rsshub.app/bilibili/user/video/1918016728
My location is Canada, I guess bilibili server might be in China. The bug persist whether enable/disable adblock chrome extension.
Entry ID
No response
Relevant Information
https://rsshub.app/bilibili/user/video/1918016728
https://app.folo.is/share/users/220732968294292480
Reproduction Video
https://drive.google.com/file/d/1ct3XZh2K4GpsVrfxSgPa2mQjhFClvik7/view?usp=sharing
Environment
Linux
Google Chrome 143.0.7499.40
Validations
- Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
- Check that this is a concrete bug. For Q&A, please open a GitHub Discussion instead.
- This issue is valid
Contributions
- I am willing to submit a PR to fix this issue
- I am willing to submit a PR with failing tests (actually just go ahead and do it, thanks!)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the failure with the Bilibili URL https://rsshub.app/bilibili/user/video/1918016728 in the web desktop app and review the linked reproduction video. Trace where the fetching error is surfaced, then determine the expected behavior for this error; done means the subscription can be fetched successfully or the failure is handled with a clear user-facing result.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100