PUT /tracks/{track_urn} returns 500 with an empty body for purchase_url updates since 2026-10-15 14:52 UTC
还没有人认领这个 Issue。
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 15/100
- Issue 类型
- 缺陷
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 领域
- api
调研方向
The payload names only API endpoints, not repository files, so the fault is probably server-side and outside this repo. Reproduce the three PUT /tracks/... request shapes in the table with a track owner's token, and compare them with the working GET /tracks/... and POST /likes/tracks/... calls. Done means a 200 response with the updated track, or a maintainer confirming the cause and the contract change.
由索引模型根据 Issue 内容生成。
描述
Since 2026-10-15 at 14:52 UTC, every attempt by our app to set purchase_url on a track owned by the authenticated user fails with HTTP 500 and an empty response body. The same calls succeeded until that moment, with no change on our side.
Request (Authorization: OAuth <access token of the track owner>, Content-Type: application/json):
| Shape | Path | Body | Result |
|---|---|---|---|
| 1 | PUT /tracks/soundcloud:tracks:<id> |
{"track":{"purchase_url":"<url>","purchase_title":"<title>"}} |
500, empty body |
| 2 | PUT /tracks/soundcloud:tracks:<id> |
{"track":{"purchase_url":"<url>"}} |
500, empty body |
| 3 | PUT /tracks/<numeric id> |
{"track":{"purchase_url":"<url>"}} |
500, empty body |
What still works with the same tokens: GET /resolve, GET /tracks/..., POST /likes/tracks/..., POST /tracks/.../comments, POST /me/followings/....
Scale: more than 240 failed updates from different user accounts between 2026-10-15 14:52 UTC and 2026-10-16 14:45 UTC. Example timestamps (UTC): 2026-10-16T14:40:59Z, 2026-10-16T14:41:00Z, 2026-10-16T14:41:02Z.
Expected: 200 with the updated track, as before 2026-10-15 14:52 UTC.
Is this a known incident, or has the update contract for purchase_url changed?
- 主要语言
- JavaScript
- 星标
- 259
- 派生
- 54
- 平均合并
- 1 分钟
- 30 天内合并 PR
- 1
环境准备
这个项目没有提供开发容器、Dockerfile 或贡献指南，环境需要你自己搭建：先看它的 README，通用步骤见我们的新手贡献指南。
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
soundcloud/api 的其他 Issue
-
POST /tracks returns 400 "uid has already been taken" but still creates the track (since 2026-10-15)未关闭
难度 4/5 3-5 天 新手友好度 38/100
soundcloud/api#601 · 5 条评论 ·
-
enhancement
难度 5/5 一周以上 新手友好度 25/100
soundcloud/api#597 · 1 个 reaction ·
-
enhancement
难度 4/5 3-5 天 新手友好度 40/100
soundcloud/api#596 · 2 条评论 · 1 个 reaction ·
-
question
难度 4/5 3-5 天 新手友好度 45/100
soundcloud/api#595 · 4 条评论 ·
-
documentation
难度 4/5 3-5 天 新手友好度 45/100
soundcloud/api#583 · 1 条评论 · 1 个 reaction ·
相似的 Issue
-
documentation good first issue theming
难度 2/5 1-3 小时 新手友好度 85/100
-
feature
难度 2/5 1-3 小时 新手友好度 85/100
-
难度 2/5 1-3 小时 新手友好度 62/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 74/100
drevendev/PatchPitch#2 ·
-
难度 1/5 1 小时以内 新手友好度 65/100
521xueweihan/HelloGitHub#4025 ·