Hacktoberfest 2026:メンテナが10月に向けて印を付けた、オープンで初心者向けの issue。 Hacktoberfest の issue を見る

POST /tracks returns 400 "uid has already been taken" but still creates the track (since 2026-10-15)

オープン
#601 コメント 2 件 リアクション 0 件 担当者 0 名 GitHub で見る

まだ誰も着手していません。

評価

難易度
4/5
見積もり時間
3〜5日
初心者へのやさしさ
38/100
issue の種類
バグ
明瞭さ
おおむね明確
活発さ
活発
技術スタック
javascript
領域
api, backend

調査の方向性

The report describes a regression in POST /tracks: uploads return 400 with “uid has already been taken” even though tracks are created. Start by comparing the behavior before and after 2026-10-15 and reviewing the related issue #600. Done means the API returns 201 with the created track, or documents a supported way to retrieve its URN.

索引モデルが issue の本文から書いたものです。

説明

Since 2026-10-15, every track upload from our app via POST https://api.soundcloud.com/tracks returns HTTP 400 with the body below, but the track is created and finishes processing. The same request returned 201 with the track until 2026-10-14. Nothing changed on our side (same build, same OAuth app, same request shape).

This looks like the same incident mentioned in #600 (comment by @Lorenzo-Biondi). Opening separately because #600 is about PUT /tracks/{urn} returning 500.

Request (Authorization: OAuth <access token of the account owner>, multipart/form-data):

Field Value
track[asset_data] MP3, ~4–5 MB
track[title] e.g. Listen to the article: What is a forward-deployed engineer?
track[sharing] public

Response:

HTTP 400 Bad Request
{"code":400,"message":"uid has already been taken","link":"https://developers.soundcloud.com/docs/api/explorer/open-api","status":"400 - Bad Request","errors":[{"error_message":"uid has already been taken"}],"error":null}

Timeline (UTC):

Window Result
2026-10-09 → 2026-10-14 15:17 9 uploads, all 201 with the track
2026-10-15 19:41 → now every upload 400 uid has already been taken (one 500 at 2026-10-15 19:44:45)

The OAuth token refresh (POST https://secure.soundcloud.com/oauth/token) keeps returning 200 throughout, and updates via PUT /tracks/{urn} were working until 2026-10-14.

Tracks created despite the 400 (account soundcloud.com/mckinsey; each URN maps to one "failed" request at the listed time):

Request time (UTC) Track created
2026-10-16 19:20:30 soundcloud:tracks:2420541609
2026-10-16 19:21:45 soundcloud:tracks:2420541999
2026-10-16 19:23:53 soundcloud:tracks:2420542809

Impact: because the response is an error, the client cannot learn the new track's URN, and any retry creates another public duplicate.

Expected: 201 with the created track, as before 2026-10-15.

Questions:

  1. Is this a known incident, and is there an ETA?
  2. Until it is fixed, is there a supported way to get the URN of the track created by a request that returned this 400?

Client ID and further request timestamps available on request.

主要言語
JavaScript
スター
259
フォーク
54
平均マージ
1分
マージ済み PR(30日)
1

環境構築

このプロジェクトには開発コンテナ、Dockerfile、コントリビューションガイドがありません。まず README を読み、一般的な手順ははじめてのコントリビューションガイドを参照してください。

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

soundcloud/api のほかの issue

soundcloud/api の issue をすべて見る

似ている issue

JavaScript の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。