Tracks not returned for a user, even with blocked filter enabled
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 254
- Forks
- 53
- PR merge metrics
- No merged PRs in 30d
Description
Title: Tracks not returned for a user, even with blocked filter enabled
Issue found of: 13th May 2021
Endpoint(s):
GET /users/21350278/tracks
Scope(s):
Both:
- None (application is not using authentication i.e., implicit flow)
- User OAUTH
Steps to reproduce:
curl --request GET \
--url 'https://api.soundcloud.com/users/21350278/tracks?limit=200&linked_partitioning=true&client_id=DONT_SHARE_CLIENT_ID&access=playable,preview,blocked'
Expected behaviour:
A list of tracks, including tracks which are blocked.
Actual behaviour:
If called with no user OAuth scope, no tracks will be returned - however the tracks can be viewed on the user profile: https://soundcloud.com/adamtrxu/tracks
If called with a user OAuth scope, private tracks are returned, but none of the public tracks listed on the profile.
The question here is that the new high level metadata changes were made to enable us to view blocked tracks, but in this particular case, nothing is returned on the API (see https://github.com/soundcloud/api/issues/1)
Contributor guide
No contributing guide indexed for this repository
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 GET /users/21350278/tracks with the curl request shown, testing both unauthenticated and user OAuth scopes. Compare the results with the expected blocked-track behavior and review the related api/issues/1 discussion; done would require the API to return the appropriate public and blocked tracks or document the confirmed limitation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- api
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100