"Developer has not signed agreement" when run snap push
Metadata
Current evaluation
Acknowledged UX gap: unsigned publishers get an opaque 403; the agreement URL is still absent, and the old `snapcraft push` command is now a removed alias for `upload`.
Suggested action: keep open
Reason: The report gives the exact 403 payload and remediation URL, and maintainer @~noise explicitly agreed that the URL should make the error actionable. Current code has no agreements URL, while `push` is now a removed alias for `upload`, so the enhancement remains valid but should be adapted to the current upload flow.
Evaluated by: mr-cal-bot
Impact:
32
Quick Win:
18
Complexity:
30
Confidence:
88
Actionability:
82
Issue body
when I am trying to run snapcraft push xxx.snap, I got the error message like Received 403:'{"error_list": [{"message": "Developer has not signed agreement.", "code": "user-not-ready"}]}'
At first I thought maybe I need to go to sign developer code of launchpad, but in IRC channel I got I need to go to https://myapps.developer.ubuntu.com/dev/agreements/new/
in case of misunderstanding, I suggest to add this link in error message and let user know what they should do next step.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha |
Impact:
32
Quick Win:
18
Complexity:
30
Confidence:
88
Actionability:
82
|
keep open | Acknowledged UX gap: unsigned publishers get an opaque 403; the agreement URL is still absent, and the old `snapcraft push` command is now a removed alias for `upload`. | |
| stealth/space-bunny-alpha |
Impact:
35
Quick Win:
20
Complexity:
25
Confidence:
86
Actionability:
78
|
keep open | A 403 user-not-ready response lacks a direct developer-agreement link; a maintainer agreed the error should be more actionable, and no current handling was found. | |
| qwen/qwen3.6-35b-a3b |
Impact:
20
Quick Win:
13
Complexity:
20
Confidence:
80
Actionability:
80
|
keep open | Request to improve error message for 'Developer has not signed agreement' by adding a link to the agreements page | |
| qwen/qwen3.8-27b |
Impact:
20
Quick Win:
17
Staleness:
100
Complexity:
15
Confidence:
65
Support Request:
40
|
close stale | 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. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
98
Complexity:
15
Confidence:
90
Support Request:
10
|
close stale | Suggests adding a direct link to the developer agreement page in the snapcraft push error message. Unaddressed for nearly 10 years. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
98
Complexity:
15
Confidence:
90
Support Request:
20
|
close stale | User reports a 403 error during snap push stating developer agreement not signed. Suggests adding a help link to the error message. Untriaged, inactive for ~10 years. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
98
Complexity:
15
Confidence:
90
Support Request:
20
|
close stale | Suggests adding a link to the developer agreement page in the snapcraft push error message. Issue is unlabelled, has no maintainer response, and is nearly a decade old. |
Update history
| Date | Change |
|---|---|
| created |
Related issues
No related issues found above the similarity threshold.