Snapcraft should warn if it produces a snap that the store will reject
Metadata
Current evaluation
Requests local warnings for Snap Store rejection conditions. The reported permission failure is concrete, but mode validation is absent from current linters and broader local store-check work remains open.
Suggested action: needs triage
Reason: The report provides a concrete rejection involving rwxrwsr-x permissions, while repository linters cover classic, GPU, library, and metadata checks but not artifact modes. Related issue #1919397 remains open and states that local store checks are unimplemented; with no labels, assignee, or maintainer response here, consolidation and prioritization are still needed.
Evaluated by: mr-cal-bot
Impact:
52
Quick Win:
12
Complexity:
63
Confidence:
89
Actionability:
62
Issue body
It seems like there is a mismatch between the snapcraft tool and the store's review logic such that I can build a snap via snapcraft and have no indication there is a problem until I upload it to the store.
Is there a way to normalize that logic so snapcraft can warn me before/during/after the build process with what problems I might need to address before attempting an upload?
For example, I had a snap that was getting rejected with the following error:
found errors in file output: unable to read or access files in 'squashfs-root' due to mode 'rwxrwsr-x', unable to read or access files in 'squashfs-root/meta' due to mode 'rwxrwsr-x', unusual mode 'rwxrwsr-x' for entry './meta/gui', unusual mode 'rwxrwsr-x' for entry './snap', unusual mode 'rwxr-sr-x' for entry './snap/.AppleDouble' security-snap-v2_squashfs_files
It would be nice if snapcraft output a similar warning when the snap was built.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha |
Impact:
52
Quick Win:
12
Complexity:
63
Confidence:
89
Actionability:
62
|
needs triage | Requests local warnings for Snap Store rejection conditions. The reported permission failure is concrete, but mode validation is absent from current linters and broader local store-check work remains open. | |
| stealth/space-bunny-alpha |
Impact:
45
Quick Win:
8
Complexity:
65
Confidence:
75
Actionability:
50
|
needs triage | Requests that snapcraft warn at build time about store-rejection problems (e.g. setgid-bit modes like 'rwxrwsr-x' triggering security-snap-v2_squashfs_files). Linter framework exists but has no permission/squashfs checks. Untriaged, no maintainer response. | |
| stealth/space-bunny-alpha |
Impact:
45
Quick Win:
10
Complexity:
60
Confidence:
72
Actionability:
58
|
needs triage | Request for snapcraft to warn at build/pack time about store upload rejections (e.g. setgid rwxrwsr-x file modes caught by security-snap-v2_squashfs_files); no permission linter exists and no maintainer triage recorded. | |
| stealth/space-bunny-alpha |
Impact:
46
Quick Win:
9
Complexity:
63
Confidence:
89
Actionability:
55
|
needs triage | Longstanding request for build-time store-rejection warnings; local linting now runs before pack but lacks the reported permission check, with no maintainer triage recorded. | |
| qwen/qwen3.8-27b |
Impact:
30
Quick Win:
16
Staleness:
92
Complexity:
45
Confidence:
72
Support Request:
10
|
close stale | Feature request for snapcraft to warn during/after build about store-rejection issues like unusual file modes. No maintainer activity in 8 years. The snapcraft lint command (PRs #4095, #4115) now provides pre-upload checks. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
95
Complexity:
50
Confidence:
80
Support Request:
10
|
needs triage | Feature request to add pre-upload validation warnings in snapcraft for store rejections like unusual file modes. Unlabelled, zero comments, and inactive for nearly 8 years. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
98
Complexity:
40
Confidence:
90
Support Request:
10
|
needs triage | Feature request to add build-time warnings for potential store rejections. Currently untriaged with no maintainer interaction or activity for nearly eight years. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
98
Complexity:
60
Confidence:
85
Support Request:
5
|
close stale | Feature request to have snapcraft validate snap contents against store review rules during build, preventing late-stage upload rejections. Unaddressed for over 7 years with no maintainer interaction. |
Update history
| Date | Change |
|---|---|
| created |
Related work
-
Duplicate Of:
snapcraft (launchpad)#1919397
(confidence 90%)
Later open issue covers the same absence of local store checks and upload-time rejection feedback.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1871109 snapcraft should check file creation permissions and warn/error out instead of generating a non-functional snap | snapcraft (launchpad) | closed | Snapcraft now validates the snap skeleton and fails before producing an unusable artifact; merged in canonical/snapcraft#3743 (7c927032d). |