Cant build snaps with snapcraft when snap store is down
Metadata
Current evaluation
Reported Snap Store outages can block builds; maintainers identified refresh, base, extension, injection, and default-provider paths, but no complete fix or current reproducer is documented.
Suggested action: keep open
Reason: The issue is valid and maintainer-triaged: the 2021 comment scoped build-snap, base, desktop-extension, and injection refreshes, while the 2023 comment added default-provider validation. Related issue #1869506 received fixes in 7ab76e084 and 4c63e5937, and canonical/snapcraft#3593 added offline network-operation skips, but these do not establish that all reported paths now recover automatically; the missing current version and reproducer reduce actionability.
Evaluated by: mr-cal-bot
Issue body
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha |
Impact:
58
Quick Win:
12
Complexity:
67
Confidence:
84
Actionability:
61
|
keep open | Reported Snap Store outages can block builds; maintainers identified refresh, base, extension, injection, and default-provider paths, but no complete fix or current reproducer is documented. | |
| stealth/space-bunny-alpha |
Impact:
60
Quick Win:
9
Complexity:
75
Confidence:
78
Actionability:
62
|
keep open | Snapcraft builds can fail when Snap Store refreshes or provider checks are unavailable; maintainers identified several affected paths, but no resolution or current reproducer is documented. | |
| qwen/qwen3.6-35b-a3b |
Impact:
70
Quick Win:
25
Complexity:
40
Confidence:
55
Actionability:
60
|
needs triage | Snapcraft blocks local builds when Snap Store is unreachable, requiring network connectivity for store update checks even during offline development builds | |
| qwen/qwen3.8-27b |
Impact:
45
Quick Win:
18
Staleness:
80
Complexity:
60
Confidence:
55
Support Request:
15
|
needs triage | Snapcraft blocks snap rebuilds when the Snap Store is unreachable, forcing developers to use a /run/.containerenv workaround; reporter suggests snapcraft should proceed with the build. Untriaged, 0 comments, last activity ~3.4 years ago. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
95
Complexity:
40
Confidence:
85
Support Request:
15
|
close stale | Snapcraft fails to build when the Snap Store is unreachable due to mandatory network checks. The report is over five years old with no maintainer response or comments. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
95
Complexity:
20
Confidence:
85
Support Request:
10
|
close stale | snapcraft fails to build snaps when the Snap Store is unreachable due to forced connection checks. Issue is 5+ years old with no maintainer response. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
95
Complexity:
30
Confidence:
85
Support Request:
10
|
close stale | Reports snapcraft failing to build when Snap Store is unreachable due to forced update checks. No maintainer response in over 3 years. Workaround exists. |
Update history
| Date | Change |
|---|---|
| created |
Related work
-
Related To:
snapcraft (launchpad)#2012057
(confidence 99%)
Explicitly cited in the 2023 comment as the default-provider validation path; it was closed through canonical/snapcraft#4096, but addressed channel syntax rather than store availability.
-
Related To:
snapcraft (launchpad)#1869506
(confidence 96%)
Closely overlapping offline-store crash fixed by canonical/snapcraft#3502 and follow-up commit 4c63e5937, although later Snapcraft versions reportedly still experienced related crashes.
-
Related To:
canonical/snapcraft#3593
(confidence 90%)
Commit edb9e2864 made lifecycle and provider code skip network operations in offline mode, matching several scenarios without proving complete automatic recovery.
Related issues
No related issues found above the similarity threshold.