Confusing error message on expired macaroon
Metadata
Current evaluation
craft-store shows a confusing 'macaroon-permission-required' error when store credentials expire instead of telling users to re-login. Triaged by a maintainer with a Jira ticket (CRAFT-3385), but no code work; last activity ~11 months ago.
Suggested action: keep open
Reason: The issue carries 'Status: Triaged' and 'Type: Bug' labels, the maintainer (sergiusens) proposed a concrete approach (client-side expiration check via the exported creds), and an internal Jira ticket CRAFT-3385 was created in Sept 2024 — so it is acknowledged and scoped, not stale-dead. No evidence the fix landed, and the confusing error on expired credentials is still a real UX problem, so it should stay open despite ~11 months of inactivity.
Issue body
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.8-27b |
Impact:
35
Quick Win:
21.0
Staleness:
65
Complexity:
40
Confidence:
70
Support Request:
10
|
keep open | craft-store shows a confusing 'macaroon-permission-required' error when store credentials expire instead of telling users to re-login. Triaged by a maintainer with a Jira ticket (CRAFT-3385), but no code work; last activity ~11 months ago. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
60
Complexity:
25
Confidence:
85
Support Request:
10
|
keep open | Improving error messaging for expired store credentials. The issue is triaged, acknowledged by a maintainer, and scoped as a bug, but has seen no activity for ~10 months. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
70
Complexity:
25
Confidence:
80
Support Request:
5
|
keep open | Triaged bug reporting a confusing error message when a macaroon expires. Maintainer suggested a client-side check, but no implementation or follow-up in nearly a year. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
75
Complexity:
20
Confidence:
80
Support Request:
10
|
keep open | Confusing error messages appear when store macaroon credentials expire. Maintainers propose a client-side expiration check for clearer feedback. Triaged and awaiting implementation, with an internal Jira ticket created. |
Update history
No update history recorded yet.
Related work
-
Related To:
snapcraft (launchpad)#1745264
(confidence 75%)
Earlier report of the same unhelpful expired-macaroon error in snapcraft; closed without a formal fix, so this craft-store issue is the live tracking point.
-
Related To:
snapcraft (launchpad)#1834469
(confidence 70%)
Open request to improve error messaging for invalid/expired macaroons in snapcraft, same underlying UX gap.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1834469 error messaging for invalid macaroon could be improved | snapcraft (launchpad) | open | Snapcraft shows a confusing 'missing a valid macaroon' error when the store macaroon expires; suggests guiding users to snapcraft login. 7 years old, no labels, no comments, no maintainer response. Related craft-store#97 tracks the same problem class. | |
| #1745264 error message for expired macaroon is not helpful | snapcraft (launchpad) | closed | Closed without discussion or a formal fix. The report highlighted an unhelpful 401 error for an expired Travis CI macaroon during snap uploads, likely resolved by updating credentials or abandoned. | |
| #1930592 Handle macaroon-authorization-required error response | snapcraft (launchpad) | open | snapcraft whoami shows a generic 'Store Error: whoami failed.' instead of prompting re-authentication when credentials are missing/expired (401 macaroon-authorization-required). Open since 2021, zero comments, no maintainer activity or labels. | |
| #4411 Store spread tests failing | snapcraft | closed | Store spread tests failed due to an expired macaroon authentication token. The issue was fixed and closed after a maintainer confirmed the resolution on May 7, 2024. |