Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

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

Cerrado
  • ¿Algo no está bien?
#601 5 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
38/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
javascript
Área
api, backend

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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.

Lenguaje dominante
JavaScript
Estrellas
259
Forks
54
Merge medio
1 min
PR fusionados (30 d)
1

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de soundcloud/api

Todos los issues de soundcloud/api

Issues similares

Más issues de JavaScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.