No explicit error message when trying to push the same snap twice
Metadata
Current evaluation
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.
Suggested action: keep open
Reason: Maintainer ~elopio confirmed that the generic retry advice is wrong, and ~sergiusens said support for the Store's new error messages was still needed. The current client still maps processing_error to the generic “error while processing” status, and no resolving commit, PR, or release is identified.
Evaluated by: mr-cal-bot
Impact:
32
Quick Win:
17
Complexity:
35
Confidence:
87
Actionability:
84
Issue body
When I push the same snap twice, the store status tracker replies with:
A file with this exact same content has already been uploaded
However, snapcraft only says:
There has been a problem while analyzing the snap, check the snap and try to push again.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha |
Impact:
32
Quick Win:
17
Complexity:
35
Confidence:
87
Actionability:
84
|
keep 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. | |
| stealth/space-bunny-alpha |
Impact:
32
Quick Win:
26
Complexity:
12
Confidence:
99
Actionability:
94
|
close resolved | Duplicate pushes hid the Store's explicit “already uploaded” error behind generic retry guidance; PR #1110 fixed Snapcraft to expose status-tracker error messages. | |
| qwen/qwen3.6-35b-a3b |
Impact:
40
Quick Win:
19
Complexity:
20
Confidence:
50
Actionability:
60
|
close resolved | Generic error message when pushing duplicate snap; store provides clear message but snapcraft shows unhelpful generic error | |
| qwen/qwen3.8-27b |
Impact:
15
Quick Win:
12
Staleness:
100
Complexity:
20
Confidence:
70
Support Request:
0
|
close stale | 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. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
98
Complexity:
15
Confidence:
85
Support Request:
0
|
close stale | Reports a generic error message in snapcraft when pushing a duplicate snap, instead of showing the store's explicit upload message. Issue is over 9 years old with no activity or maintainer response. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
98
Complexity:
10
Confidence:
85
Support Request:
5
|
close stale | Generic error message when pushing duplicate snaps. No maintainer interaction or updates in over 9 years. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
98
Complexity:
15
Confidence:
85
Support Request:
10
|
close stale | snapcraft displays a generic error instead of the explicit store message when pushing an already uploaded snap. Unaddressed for nearly a decade with no maintainer interaction or reproduction steps. |
Update history
| Date | Change |
|---|---|
| created |
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1683536 snapcraft uploaded snap and then told me same content had already been uploaded | snapcraft (launchpad) | 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. |