You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Linux version 6.8.0-1013-oracle (buildd@lcy02-amd64-031) (x86_64-linux-gnu-gcc-13 (Ubuntu 13.2.0-23ubuntu4) 13.2.0, GNU ld (GNU Binutils for Ubuntu) 2.42); Docker version 27.3.1, build ce12230
额外信息
Looks like something went wrong
Helpful Information
Error Message:
FetchError: [GET] "https://api.spotify.com/v1/playlists/37i9dQZF1DXcBWIGoYBM5M": 404 Not Found
Route: /spotify/playlist/:id
Full Route: /spotify/playlist/37i9dQZF1DXcBWIGoYBM5M
Node Version: v22.11.0
Git Hash: d042b63c
Git Date: Tue, 26 Nov 2024 15:20:38 GMT
To maintainers: if you are not willing to be disturbed, list your username in scripts/workflow/test-issue/call-maintainer.js. In this way, your username will be wrapped in an inline code block when tagged so you will not be notified.
If all routes can not be found, the issue will be closed automatically. Please use NOROUTE for a route-irrelevant issue or leave a comment if it is a mistake.
如果所有路由都无法匹配,issue 将会被自动关闭。如果 issue 和路由无关,请使用 NOROUTE 关键词,或者留下评论。我们会重新审核。
路由地址
完整路由地址
相关文档
https://docs.rsshub.app/routes/multimedia#playlist
预期是什么?
订阅该路由可以正常获得 playlist 的更新
实际发生了什么?
报错返回 404 Not Found
如果订阅的是普通用户的 playlist 则可以正常抓取,比如:
但是如果是 Spotify 官方的 playlist 则报错返回 404 Not Found,比如:
我尝试了使用 rsshub.app 和自建两种方式,同样的问题
部署
自建
部署相关信息
Linux version 6.8.0-1013-oracle (buildd@lcy02-amd64-031) (x86_64-linux-gnu-gcc-13 (Ubuntu 13.2.0-23ubuntu4) 13.2.0, GNU ld (GNU Binutils for Ubuntu) 2.42); Docker version 27.3.1, build ce12230
额外信息
Looks like something went wrong Helpful Information Error Message: FetchError: [GET] "https://api.spotify.com/v1/playlists/37i9dQZF1DXcBWIGoYBM5M": 404 Not Found Route: /spotify/playlist/:id Full Route: /spotify/playlist/37i9dQZF1DXcBWIGoYBM5M Node Version: v22.11.0 Git Hash: d042b63c Git Date: Tue, 26 Nov 2024 15:20:38 GMT
这不是重复的 issue
The text was updated successfully, but these errors were encountered: