Snapcraft 7.1.1 gives vague error when it can't process package
Metadata
Current evaluation
Vague 'Service unavailable' on snapcraft upload. The text originates from the store's processing pipeline, not Snapcraft; Snapcraft already relays store error messages verbatim. Self-resolved for the reporter after `snapcraft clean`; root cause never diagnosed.
Suggested action: close not a bug
Reason: "Service unavailable. Please try again later (d510601fa...)" is emitted by the store's processing backend, not Snapcraft — the string appears nowhere in the Snapcraft codebase. `notify_upload` (snapcraft/store/client.py ~line 661) already surfaces the store's `status["errors"]` messages verbatim via `SnapcraftError(f"Issues while processing snap:\n{error_string}")`, confirmed by the passing test `test_notify_upload_error`, so there is no vague Snapcraft-side message to improve. The reporter's own follow-up concedes resolution ("After a `snapcraft clean`, the build now is processed correctly") and the root cause was never identified, making this a transient store-side failure rather than a Snapcraft defect.
Evaluated by: mr-cal-bot
Issue body
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha |
Impact:
15
Quick Win:
2
Complexity:
30
Confidence:
78
Actionability:
20
|
close not a bug | Vague 'Service unavailable' on snapcraft upload. The text originates from the store's processing pipeline, not Snapcraft; Snapcraft already relays store error messages verbatim. Self-resolved for the reporter after `snapcraft clean`; root cause never diagnosed. | |
| stealth/space-bunny-alpha |
Impact:
28
Quick Win:
8
Complexity:
38
Confidence:
58
Actionability:
45
|
needs triage | Snapcraft 7.1.1 upload shows only 'Service unavailable. Please try again later' when the store rejects a snap; author wants a more descriptive error. Resolved for them by `snapcraft clean`, root cause never diagnosed. | |
| stealth/space-bunny-alpha |
Impact:
40
Quick Win:
13
Complexity:
45
Confidence:
87
Actionability:
58
|
needs triage | Snapcraft 7.1.1 reports only a generic service error when uploaded snap processing fails. Current code still extracts only the server message, and the report has no maintainer triage. | |
| qwen/qwen3.8-27b |
Impact:
35
Quick Win:
24
Staleness:
95
Complexity:
30
Confidence:
55
Support Request:
20
|
close stale | Snapcraft 7.1.1 returns a vague 'Service unavailable' error when snap upload processing fails, making it hard for users to diagnose the root cause. No maintainer response or labels; issue is 4 years old. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
95
Complexity:
40
Confidence:
90
Support Request:
25
|
close stale | Reports vague 'Service unavailable' error during snap upload in Snapcraft 7.1.1 and requests better error messaging. Unlabelled and inactive for over 4 years. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
95
Complexity:
30
Confidence:
85
Support Request:
20
|
close stale | Report of vague upload error in Snapcraft 7.1.1 requesting better error messages. Unlabelled, zero maintainer comments, and inactive for over four years. Likely outdated given current Snapcraft versions. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
95
Complexity:
20
Confidence:
85
Support Request:
10
|
close stale | User reports a vague Service unavailable error during snap upload in version 7.1.1, requesting more concrete error messages. Issue has seen no maintainer interaction in nearly four years. |
Update history
| Date | Change |
|---|---|
| created |
Related issues
No related issues found above the similarity threshold.