Error when trying to register a reserved name is missing a sentence
Metadata
Current evaluation
Fixed in canonical/snapcraft#629 via commit 250a350b9, which completed the reserved-name registration error guidance.
Resolution: closed resolved
Reason: Commit 250a350b9 (“Proper message when registering a reserved snap,” PR #629) added the requested naming guidance and resolved the issue.
Evaluated by: mr-cal-bot
No scores available.
Issue body
From the snapcraft UX doc, the error should finish with:
Please register a name that people will associate with you.
We can rename your snap later if needed.
The current error message is:
The name 'bash' is reserved.
If you are the publisher most users expect for 'bash' then please claim the name at 'https://myapps.developer.ubuntu.com/dev/click-apps/register-name-dispute/?series=16&name=bash'
To reproduce:
snapcraft register bash
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha | — | closed resolved | Fixed in canonical/snapcraft#629 via commit 250a350b9, which completed the reserved-name registration error guidance. | |
| stealth/space-bunny-alpha | — | closed resolved | Fixed by canonical/snapcraft#629 (commit 250a350b9), which added the requested guidance to the reserved-name registration error. | |
| stealth/space-bunny-alpha | — | closed resolved | Fixed by merged PR canonical/snapcraft#1778 (881a79405), restoring the missing guidance in the reserved-name registration error. | |
| qwen/qwen3.6-35b-a3b | — | — | Fixed by updating the reserved name registration error message to include the missing guidance sentence. The issue was closed after the text change was merged. | |
| qwen/qwen3.6-35b-a3b | — | — | Fixed. The reserved name registration error message was updated to include the missing guidance sentence, resolving the UX discrepancy. | |
| qwen/qwen3.6-35b-a3b | — | — | The reserved name registration error message was updated to include the missing guidance about choosing an associateable name and later renaming. The issue was closed after the fix was applied. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Fixed the reserved name registration error message by adding the missing guidance sentence. The updated output now directs users to claim the name or register an alternative. |
Update history
| Date | Change |
|---|---|
| created |
Related work
-
Likely Fixed By:
canonical/snapcraft#629
(confidence 99%)
Commit 250a350b9 implements the missing reserved-name registration messaging.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1598932 Trying to register a snap already reserved doesn't explain the error cause | snapcraft (launchpad) | closed | Fixed by snapcore/snapcraft#629, merged as commit 250a350b9, adding a clearer message when registering a reserved snap name. | |
| #1778 Add sentences to error when registering name | snapcraft | merged | Merged as snapcraft/snapcraft#1778 (commit 881a79405): extends the reserved-name registration error with extra guidance and 'choose a different name', addressing LP bug #1602791. | |
| #629 Proper message when registering an already registered snap | snapcraft | merged | Merged as commit 250a350b9, adding clearer handling and dispute guidance for registering a reserved snap name after the already-registered-name fix in #623. | |
| #1644673 Trying to register a snap name with reserved characters fails opaquely | snapcraft (launchpad) | closed | Invalid snap names now produce a detailed allowed-character error. The handling landed in PR #1247 (03105a6c4), and Snapcraft v2.34 was confirmed to display it. | |
| #1740500 "The name <foo> is already taken" is a poor experience | snapcraft (launchpad) | open | The reported reserved-name wording is absent from current code: ffb164b7a removed snapcraft_legacy, and the modern register command no longer contains the quoted message. |