Trying to register a snap already registered doesn't explain the error cause
Metadata
Current evaluation
Added a clearer error for duplicate snap registration in snapcore/snapcraft PR #623, commit fca736b61.
Resolution: closed resolved
Reason: Resolved by snapcore/snapcraft PR #623 in commit fca736b61, titled "Proper message when registering an already registered snap." The maintainer linked that PR as the issue's resolution.
Evaluated by: mr-cal-bot
No scores available.
Issue body
When I try to register a snap that I registered previously, an error is returned:
Registration failed.
This error should explain that the name is already registered by the user and snaps of that name can just be uploaded.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha | — | closed resolved | Added a clearer error for duplicate snap registration in snapcore/snapcraft PR #623, commit fca736b61. | |
| stealth/space-bunny-alpha | — | closed resolved | Fixed by snapcore/snapcraft#623, adding a clearer error when a snap name is already registered by the user. | |
| stealth/space-bunny-alpha | — | closed resolved | Fixed by merged PR #623 (commit fca736b61), improving the error shown when registering an already-registered snap name. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed without implementation. The vague error message for already registered snaps was never updated. No pull request or fix was submitted, indicating the report was abandoned. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed without resolution. The vague registration error for already-registered snaps was not addressed. The report was abandoned due to inactivity. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed without resolution. The generic registration error for already registered snaps remains unaddressed, with no fix or follow-up provided. |
Update history
| Date | Change |
|---|---|
| created |
Related work
-
Likely Fixed By:
snapcore/snapcraft#623
(confidence 100%)
The linked PR implements the requested clearer message and maps to commit fca736b61.
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. | |
| #1598939 registering too many snaps in a short time period fails without a proper error | snapcraft (launchpad) | closed | Fixed by merged snapcore/snapcraft#630 (commit 1a5ff1f98), adding a clear error when snap registration is attempted too quickly. | |
| #623 Proper message when registering an already registered snap | snapcraft | merged | Merged PR #623 (commit fca736b61, LP #1596782) improving the error shown when registering an already-registered snap name, pointing at the name-dispute claim form. | |
| #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. | |
| #6213 fix(register): link to snap registration docs | snapcraft | merged | Merged PR #6213 fixes #5042 in commit 39f7a1f43, adding a registration how-to link to snapcraft register output. | |
| #630 Report a nice error when registering too fast | snapcraft | merged | Merged as 1a5ff1f98, adding a clear error when snap registration is attempted too soon and building on #629's already-registered-name handling. | |
| #1602091 Trying to register a snap I registered before points to the dispute form | snapcraft (launchpad) | closed | Fixed by merged PR #942 (commit 2bc1ec109), which added specific handling for registering a snap already owned by the user. |