trying to upload a snap without signing the agreement prints the error twice
Metadata
Current evaluation
Snapcraft upload command prints the 'Developer has not signed agreement' error twice (once in red, once in green) when a user has not signed the store agreement. Suggests cleaning up output so Reason/Text only show with -d flag. Open since 2016 with no comments or maintainer response.
Suggested action: needs triage
Reason: The issue is 10 years old with zero comments and no maintainer interaction, but it describes a real (if minor) UX bug in error output formatting. It has never been triaged, labelled, or acknowledged. The upload command has been substantially refactored since 2016 (commits like 'cli: migrate upload and release to new channel-map' and 'storeapi: update api and error messages from push to upload'), so the exact error strings may no longer exist in the codebase. A maintainer should verify whether the duplicate output still occurs in the current code before deciding to fix or close.
Issue body
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.8-27b |
Impact:
20
Quick Win:
17.0
Staleness:
95
Complexity:
15
Confidence:
55
Support Request:
5
|
needs triage | Snapcraft upload command prints the 'Developer has not signed agreement' error twice (once in red, once in green) when a user has not signed the store agreement. Suggests cleaning up output so Reason/Text only show with -d flag. Open since 2016 with no comments or maintainer response. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
98
Complexity:
15
Confidence:
95
Support Request:
5
|
close stale | Duplicate error output when uploading a snap without a signed agreement. Suggests suppressing verbose details unless debug flag is used. Issue has been inactive for over 9 years with no maintainer response. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
95
Complexity:
15
Confidence:
90
Support Request:
0
|
close stale | Minor CLI UX issue where uploading a snap without a signed agreement prints duplicate error messages. Issue is over 9 years old with no maintainer interaction or updates. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
98
Complexity:
15
Confidence:
85
Support Request:
5
|
close stale | CLI prints duplicate error messages when uploading a snap without a signed agreement. Issue is over 10 years old with no activity or maintainer response. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
98
Complexity:
20
Confidence:
90
Support Request:
5
|
close stale | Duplicate errors appear when uploading a snap without signing the developer agreement. Suggests hiding detailed store responses unless verbose mode is enabled and standardizing error color. Open, unassigned, awaiting triage. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1624854 "Developer has not signed agreement" when run snap push | snapcraft (launchpad) | open | User hit 403 'Developer has not signed agreement' (user-not-ready) on snapcraft push, resolved via IRC by signing at myapps.developer.ubuntu.com. Suggests adding that link to the error message. 10 years old, no maintainer activity. | |
| #1542476 snapcraft upload forbidden for user without signed agreement | snapcraft (launchpad) | closed | Closed as expected behavior. No code changes were made. Users must sign the Snap Store agreement before uploading snaps to resolve the forbidden error. |