snapcraft uploaded snap and then told me same content had already been uploaded
Metadata
Current evaluation
Store rejects duplicate snap content only after the full upload; the requested preflight hash check needs a new Store API. Maintainer confirmed the store-side limitation in 2017; still open with no Snapcraft-side fix.
Suggested action: keep open
Reason: The report is a valid, cleanly reproduced UX problem ("It would have been nice if I didn't have to wait for the snap to upload before getting this error message") and it was assessed by a maintainer: ~kyrofa replied that "Snapcraft isn't the one telling you this, it's the store... the store will need to grow an API for it." It therefore stays open, but it is not actionable by Snapcraft alone — the fix is a Store-side preflight-hash API, so complexity is high and actionability low. Impact is limited to wasted upload time on a rare mistake, not a broken workflow. Note the nearby PR canonical/snapcraft#1009 (pre-check for unregistered snap names, commit 8d7b53aa3) does not address duplicate content, and the sibling bug #1619818 was only partially addressed by PR #1110 surfacing status-tracker errors.
Evaluated by: mr-cal-bot
Issue body
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha |
Impact:
22
Quick Win:
2
Complexity:
72
Confidence:
68
Actionability:
35
|
keep open | Store rejects duplicate snap content only after the full upload; the requested preflight hash check needs a new Store API. Maintainer confirmed the store-side limitation in 2017; still open with no Snapcraft-side fix. | |
| stealth/space-bunny-alpha |
Impact:
30
Quick Win:
5
Complexity:
70
Confidence:
90
Actionability:
55
|
keep open | Duplicate snap uploads are rejected only after the full transfer; the requested store preflight API remains unresolved, with no Snapcraft fix recorded. | |
| qwen/qwen3.6-35b-a3b |
Impact:
20
Quick Win:
10
Complexity:
30
Confidence:
60
Actionability:
70
|
needs triage | snapcraft push reports duplicate content error only after full upload completes, wasting bandwidth and time. Issue is from 2017 with no maintainer response or labels. | |
| qwen/qwen3.8-27b |
Impact:
15
Quick Win:
10
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. |
Update history
| Date | Change |
|---|---|
| created |
Related work
-
Related To:
snapcraft (launchpad)#1619818
(confidence 82%)
Same underlying scenario (pushing a snap whose content the store already has); per the corpus, PR #1110 fixed only the hiding of the store's explicit error behind generic retry guidance, not the duplicate-detection timing.
-
Related To:
canonical/snapcraft#1009
(confidence 70%)
Merged commit 8d7b53aa3 adds a snapcraft push pre-check so unregistered snap names error before upload — related in spirit but only covers name registration, not duplicate binary content.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1619818 No explicit error message when trying to push the same snap twice | snapcraft (launchpad) | open | Acknowledged duplicate-upload UX bug: Snapcraft can show a generic processing error instead of the store's explicit “same content already uploaded” message; no resolving change is identified. |