snapcraft uploaded snap and then told me same content had already been uploaded
Metadata
Current evaluation
2017 request to detect duplicate snap content before uploading, since `snapcraft push` only reports the store's 'already been uploaded' error after a full upload. No labels or comments. The push command was later removed from snapcraft.
Suggested action: close stale
Reason: The issue has had zero comments, no labels, and no maintainer interaction for ~9 years (last activity 3213 days ago), and the `snapcraft push` command it targets was removed in snapcraft 4.x in favor of `snapcraft upload`/`release`, so the reported flow no longer exists. The duplicate rejection is store-side behavior working as intended, and a pre-upload hash check would require store API support rather than a client-side fix.
Impact:
15
Quick Win:
9.75
Staleness:
95
Complexity:
35
Confidence:
70
Support Request:
35
Issue body
$ snapcraft push apport-bdmurray_2017.04.17.3_amd64.snap
Pushing 'apport-bdmurray_2017.04.17.3_amd64.snap' to the store.
Uploading apport-bdmurray_2017.04.17.3_amd64.snap [ ] 0%
Uploading apport-bdmurray_2017.04.17.3_amd64.snap [========================================================================================================] 100%Error while processing...|
The store was unable to accept this snap.
- binary_sha3_384: A file with this exact same content has already been uploaded
It would have been nice if I didn't have to wait for the snap to upload before getting this error message.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.8-27b |
Impact:
15
Quick Win:
9.75
Staleness:
95
Complexity:
35
Confidence:
70
Support Request:
35
|
close stale | 2017 request to detect duplicate snap content before uploading, since `snapcraft push` only reports the store's 'already been uploaded' error after a full upload. No labels or comments. The push command was later removed from snapcraft. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
95
Complexity:
10
Confidence:
85
Support Request:
5
|
close stale | UX complaint that snapcraft uploads a snap fully before reporting a duplicate content error. Issue is over 9 years old with no maintainer response or activity. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
98
Complexity:
15
Confidence:
90
Support Request:
10
|
close stale | User reports snapcraft push completes upload but fails with a duplicate content error, requesting better error timing. No maintainer interaction, labels, or comments. Issue is over 9 years old and completely inactive. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
98
Complexity:
15
Confidence:
90
Support Request:
10
|
close stale | snapcraft push fails after 100% upload with a duplicate content error, noting the delay before the error message. Unaddressed for over 9 years. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
100
Complexity:
10
Confidence:
95
Support Request:
20
|
close stale | snapcraft push uploads the file before failing with a duplicate content error. Pre-upload validation is requested to avoid wasted time. Status: open, unassigned, inactive for nearly nine years with no comments. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1619818 No explicit error message when trying to push the same snap twice | snapcraft (launchpad) | open | Request to surface the store's 'already been uploaded' message instead of a generic error when pushing a duplicate snap. 10 years old, no activity; snapcraft push was later removed, so it is no longer applicable. |