Trying to register a snap I registered before points to the dispute form
Metadata
Current evaluation
Fixed by merged PR #942 (commit 2bc1ec109), which added specific handling for registering a snap already owned by the user.
Resolution: closed resolved
Reason: PR #942 merged as commit 2bc1ec109 and handled the store's already-owned error without misleading users toward the name-dispute process. PR #938 implemented the same fix but was closed as a duplicate of #942.
Evaluated by: mr-cal-bot
No scores available.
Issue body
I registered a snap called "test". Then I tried to register again. Snapcraft failed as expected, but it shows the error with the name dispute url, telling me that I can get hold of that name.
That is wrong, because I am the owner of the name already. The error should just say: you have already registered that name. The dispute url should only be displayed if somebody else is the owner of the name.
To reproduce:
- snapcraft register test<unique-id>
- snapcraft register test<unique-id>
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha | — | closed resolved | Fixed by merged PR #942 (commit 2bc1ec109), which added specific handling for registering a snap already owned by the user. | |
| stealth/space-bunny-alpha | — | closed resolved | Fixed by canonical/snapcraft#942 (commit 2bc1ec109), making register show the store’s specific already-owned error instead of a name-dispute URL. | |
| stealth/space-bunny-alpha | — | closed resolved | Registration messaging for an already-registered snap was corrected by merged PR #623 (commit fca736b61). | |
| qwen/qwen3.6-35b-a3b | — | — | Closed without resolution or comments, likely abandoned. The reported bug causing incorrect dispute URL display for already-registered snap names was never addressed or fixed. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed without a linked fix or resolution. The report described an incorrect dispute URL appearing when re-registering an already owned snap. No comments or pull requests were associated with the closure. |
Update history
| Date | Change |
|---|---|
| created |
Related work
-
Likely Fixed By:
canonical/snapcraft#942
(confidence 100%)
Merged resolving PR; commit 2bc1ec109 added a specific already-owned registration error.
-
Duplicate Of:
canonical/snapcraft#938
(confidence 100%)
Duplicate implementation closed because PR #942 contained the same fix.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #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. | |
| #1596782 Trying to register a snap already registered doesn't explain the error cause | snapcraft (launchpad) | closed | Added a clearer error for duplicate snap registration in snapcore/snapcraft PR #623, commit fca736b61. | |
| #1613609 Can't register name for snap package | snapcraft (launchpad) | closed | Name registration error printed an obsolete `register-name-dispute` URL (404) instead of the unified `register-name` page. Fixed by merged snapcraft PR #732 (commit fea4dfff4), removing the dispute logic from store registration. |