Validator for the snap's icon appears to check the file before the snap is compiled
Metadata
Current evaluation
Icon validation rejects packaged-container paths before building, while asset finalization supports prime-relative paths; this old, untriaged report needs assessment against current behavior.
Suggested action: needs triage
Reason: The issue has no labels, comments, assignee, or maintainer response. Current project_check.py still validates icon as a pre-build project-relative file, while setup_assets.py::_finalize_icon also supports paths under prime_dir, but the report may conflate the snap icon key with a desktop entry's Icon field, so current-version reproduction is needed.
Evaluated by: mr-cal-bot
Impact:
46
Quick Win:
17
Complexity:
43
Confidence:
89
Actionability:
66
Issue body
Running `snapcraft` with the `icon` field set to something inside the container (e.g. `share/icons/hicolor/48x48/apps/myapp.png`) results in the following validation error:
`Issues while validating snapcraft.yaml: Specified icon ./share/icons/hicolor/48x48/apps/myapp.png' does not exist`
This would suggest that the icon needs to be the relative path of the icon outside the container. However the docs seem to indicate that the icon path should be a path inside the container: https://github.com/snapcore/snapcraft/blob/master/docs/metadata.md#package-icon
In addition, running `snapcraft` with a filepath outside the container means it passes this initial validation check, but results in this error at the very end of the compilation stage:
[Errno 2] No such file or directory: './myapp/resources/appname.png' -> '/home/myuser/snap/build/dir/prime/meta/gui/icon./myapp/resources/myapp'
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha |
Impact:
46
Quick Win:
17
Complexity:
43
Confidence:
89
Actionability:
66
|
needs triage | Icon validation rejects packaged-container paths before building, while asset finalization supports prime-relative paths; this old, untriaged report needs assessment against current behavior. | |
| qwen/qwen3.6-35b-a3b |
Impact:
30
Quick Win:
13
Complexity:
40
Confidence:
70
Actionability:
70
|
keep open | Icon validation checks host filesystem before build, preventing use of icons generated during build. Also has path handling bug causing malformed destination paths. | |
| qwen/qwen3.8-27b |
Impact:
40
Quick Win:
22
Staleness:
95
Complexity:
45
Confidence:
55
Support Request:
10
|
needs triage | Snapcraft icon validator checks file existence before compilation, contradicting docs that specify container-relative paths. No maintainer response in ~10 years; unlabelled and unassessed. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
98
Complexity:
40
Confidence:
90
Support Request:
10
|
close stale | Validator incorrectly checks icon path before build environment is ready, causing false does not exist errors. Issue is 9.6 years old with no activity or maintainer response. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
98
Complexity:
45
Confidence:
92
Support Request:
15
|
close stale | Validator incorrectly checks icon path before container build, causing false validation errors or later path resolution failures. Issue is inactive for over 9 years and likely outdated. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
100
Complexity:
40
Confidence:
90
Support Request:
10
|
close stale | Reports a snapcraft validation error when the icon path points inside the build container, contradicting documentation. Issue is inactive for nearly 10 years with no maintainer response. |
Update history
| Date | Change |
|---|---|
| created |
Related issues
No related issues found above the similarity threshold.