List a Project's Release Files endpoint not returning source maps
- Dominant language
- Python
- Stars
- 44.8k
- Forks
- 4.9k
- Avg merge
- 22h 21m
- Merged PRs (30d)
- 586
Description
### Environment
SaaS ([https://sentry.io/]())
### Steps to Reproduce
1. upload source maps to a release
2. try to fetch them via API: [https://docs.sentry.io/api/releases/list-a-projects-release-files/]()
> ### Expected Result
The endpoint to return the list of uploaded endpoints
### Actual Result
Empty response:
[https://sentry.io/api/0/projects/dev-curumas/notjava/releases/finaliseTest/files/](<>)
response: \[\]
At the time of writing, this release has 6 source map/minified files uploaded
* [https://dev-curumas.sentry.io/settings/projects/notjava/source-maps/?query=finaliseTest]()
### Product Area
APIs
### Link
*No response*
### DSN
*No response*
### Version
*No response*
Contributor guide
Research direction
Start by reproducing the List a Project's Release Files endpoint described in the linked API documentation and compare its response with the source maps visible in the Sentry project. Trace the release-files API entry point and identify why uploaded source maps are omitted. Done means the endpoint lists the six uploaded release files and the relevant API behavior is covered by verification.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100