← Back to issue list

"Developer has not signed agreement" when run snap push

View original Launchpad issue

Metadata

Project
snapcraft (launchpad)
Number
#1624854
Type
issue
State
open
Author
~psivaa
Labels
Created
Updated
Closed

Current evaluation

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.

Suggested action: close stale

Reason: The issue is ~10 years old (3634 days, last activity 3624 days ago) with zero comments, no labels, and no maintainer interaction. The reporter's own problem was already resolved via IRC, and the suggested link (myapps.developer.ubuntu.com/dev/agreements/new/) points to the deprecated old store, which has since migrated to dashboard.snapcraft.io, so the specific suggestion is no longer applicable. If the error-message improvement is still wanted, it should be re-filed against the current store URL.

Impact: 20 Quick Win: 17.0 Staleness: 100 Complexity: 15 Confidence: 65 Support Request: 40

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
qwen/qwen3.8-27b
Impact: 20
Quick Win: 17.0
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.
qwen3.6-35b-a3b-mtp-q6
Staleness: 98
Complexity: 10
Confidence: 90
Support Request: 15
close stale snapcraft push returns a 403 error when the developer agreement is unsigned. Suggests improving the error message to include the signing URL and next steps. Open, unassigned, awaiting triage.

Update history

No update history recorded yet.

Related issues

Issue Project State Summary Similarity
#1596777 trying to upload a snap without signing the agreement prints the error twice snapcraft (launchpad) open 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.
73%