snapcraft reports invalid credentials after successful login (new account)
Metadata
Current evaluation
⚠️ This summary may be outdated — the issue content or evaluation prompts have changed since this evaluation was made.
Closed without resolution. The snapcraft credential and root macaroon error remains unfixed. Issue appears abandoned due to zero comments and no follow-up.
Suggested action: —
No scores available.
Issue body
this is a recently created account, I'm trying to publish a test snap using this tutorial:
https://docs.snapcraft.io/build-snaps/pre-built
when I tried to register a name it failed with this message:
Registering geekbench-user-test.
No valid credentials found. Have you run "snapcraft login"?
Invalid credentials: Root macaroon not in the config file. Have you run "snapcraft login"?
I was able to get around this by registering on the web: https://dashboard.snapcraft.io/register-snap/
but when I try to push my snap I get the same two error messages above, "No valid credentials" followed by the "Root macaroon" message.
I'm working in a fresh install of Ubuntu Desktop 18.04 running in VirtualBox. account was originally registered using Chrome on MacOS High Sierra.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.6-35b-a3b | — | — | Closed without resolution. The snapcraft credential and root macaroon error remains unfixed. Issue appears abandoned due to zero comments and no follow-up. | |
| qwen/qwen3.6-35b-a3b | — | — | Abandoned and closed without resolution. The report detailed snapcraft failing to recognize valid credentials for new accounts, blocking login and push operations. No comments or fixes were provided. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Closed without resolution. The report details snapcraft credential and root macaroon errors following login. With zero comments and no patches, the issue was abandoned. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1990888 Snapcraft login fails in text mode without Desktop | snapcraft (launchpad) | closed | Closed without resolution due to inactivity. The headless keyring dependency crash during snapcraft login remains unfixed. | |
| #1978518 login still promots for username and password when using SNAPCRAFT_STORE_CREDENTIALS | snapcraft (launchpad) | closed | Abandoned and closed without resolution due to inactivity. The reported SNAPCRAFT_STORE_CREDENTIALS login prompt bug remains unresolved. | |
| #1995488 Cannot generate new credentials (snapcraft 7.2.2->4) | snapcraft (launchpad) | open | Bug: snapcraft login fails when SNAPCRAFT_STORE_CREDENTIALS is set; never triaged, 1401 days old | |
| #2098999 Snapcraft auth does not create dir needed and errors out | snapcraft (launchpad) | open | Snapcraft auth fails to create credentials directory on macOS, causing FileNotFoundError. Issue is 560 days old with no maintainer response. | |
| #1539208 snapcraft login fails if account does not require two factor authentication | snapcraft (launchpad) | closed | Closed without a documented fix. The report indicates snapcraft login fails for accounts without two-factor authentication by incorrectly submitting an empty OTP code. | |
| #1843404 snapcraft export-login doesn't provide meaningful error messages when an argument is wrong | snapcraft (launchpad) | open | snapcraft export-login returns a generic 'Authentication error: Failed to get macaroon' instead of a meaningful message when an argument (e.g. snap name) is wrong. Unlabelled, zero comments, no maintainer interaction for ~7 years. | |
| #4226 snapcraft export-login ignores expires parameter | snapcraft | closed | Closed as stale. Maintainers clarified the short expiration is expected due to store-side macaroon refresh logic, not a snapcraft bug. No code changes were made. | |
| #1905952 Can't change snapcraft username | snapcraft (launchpad) | closed | Username synchronization between login.ubuntu.com and snapcraft.io was closed without resolution or comments, indicating the report was abandoned. No fix or workaround was provided. |