← Back to issue list

Snap package shows as registered but unable to publish

View original Launchpad issue

Metadata

Project
snapcraft (launchpad)
Number
#1853540
Type
issue
State
open
Author
~gabeduke
Labels
—
Created
Updated
Closed
—

Current evaluation

User reports kubectl-iexec snap name appears registered on their account but `snapcraft push` returns the store error 'You are not the publisher or allowed to push revisions'. The pasted `list-registered` output actually omits kubectl-iexec, and no snapcraft code path produces this message.

Suggested action: close not a bug

Reason: The error string 'You are not the publisher or allowed to push revisions for this snap' does not exist anywhere in snapcraft's source or history (grep of current tree and `git log -S` found nothing), so it is the Snap Store's own authorization response, not a client-side defect; the only related pre-check commit is 8d7b53aa3 'store: implement push pre-check'. Moreover, the `snapcraft list-registered` output pasted in the report lists leetcli, level, pileet-blink and slog but NOT kubectl-iexec, contradicting the premise that it is registered on the account — this points to an account/ownership mismatch or a name held by another account, i.e. a store support question rather than a code bug. Uncertainties: the referenced screenshot is unavailable and the report never received a maintainer response (no labels, single author comment in 2019), and the `list-registered` command has since been removed (commit 3623601d7), so the exact repro path can no longer be re-run.

Evaluated by: mr-cal-bot

Impact: 15 Quick Win: 2 Complexity: 20 Confidence: 62 Actionability: 15

Issue body

The package `kubectl-iexec` shows as registered on my account but I am unable to publish to the registered name. ``` kubectl-iexec [feature/snap●●] % snapcraft list-registered Name Since Visibility Price Notes leetcli 2017-12-31T05:31:29Z public - - level 2017-12-30T17:28:08Z public - - pileet-blink 2017-10-14T18:07:18Z public - - slog 2017-12-30T17:53:00Z public - - kubectl-iexec [feature/snap●●] % snapcraft push --release=edge kubectl-iexec_0+git.a108141-dirty_amd64.snap Preparing to push 'kubectl-iexec_0+git.a108141-dirty_amd64.snap'. After pushing, an attempt will be made to release to 'edge' You are not the publisher or allowed to push revisions for this snap. To become the publisher, run `snapcraft register kubectl-iexec` and try to push again. ``` See screenshot where the name is registered on my account.

Evaluation history

Date Model Scores Action Summary
stealth/space-bunny-alpha
Impact: 15
Quick Win: 2
Complexity: 20
Confidence: 62
Actionability: 15
close not a bug User reports kubectl-iexec snap name appears registered on their account but `snapcraft push` returns the store error 'You are not the publisher or allowed to push revisions'. The pasted `list-registered` output actually omits kubectl-iexec, and no snapcraft code path produces this message.
stealth/space-bunny-alpha
Impact: 35
Quick Win: 14
Complexity: 25
Confidence: 78
Actionability: 55
needs triage kubectl-iexec appears in list-registered, but the Store rejects upload with a publisher-permission error; the report lacks a confirmed account/ownership diagnosis or maintainer response.
stealth/space-bunny-alpha
Impact: 20
Quick Win: 6
Complexity: 30
Confidence: 84
Actionability: 40
needs triage kubectl-iexec upload is rejected for lack of publisher rights despite the user reporting that the name is registered. No code defect or maintainer assessment is documented.
qwen/qwen3.8-27b
Impact: 10
Quick Win: 9
Staleness: 95
Complexity: 10
Confidence: 70
Support Request: 90
close not a bug User reports snap name kubectl-iexec shows as registered but snapcraft push fails with 'not the publisher' error; a store account permission issue, not a snapcraft bug; 2475 days old with no maintainer response.
qwen/qwen3.6-35b-a3b
Staleness: 95
Complexity: 10
Confidence: 85
Support Request: 90
close not a bug User reports inability to publish a snap despite it showing as registered on their Snap Store account. The report lacks maintainer interaction, has no comments, and is over six years old with no updates.
qwen/qwen3.6-35b-a3b
Staleness: 98
Complexity: 15
Confidence: 90
Support Request: 85
close stale User reports inability to push a snap despite it showing as registered in their Snap Store account. Issue is over 6 years old with no maintainer interaction or updates.
qwen3.6-35b-a3b-mtp-q6
Staleness: 98
Complexity: 10
Confidence: 85
Support Request: 90
close stale User reports a Snap Store permission error when pushing a snap despite it showing as registered. Issue is over 6 years old with no maintainer response.

Update history

Date Change
created

Related issues

No related issues found above the similarity threshold.