error message for expired macaroon is not helpful
Metadata
Current evaluation
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.
Suggested action: —
No scores available.
Issue body
Exactly a year after I enabled the ci integration from travis for the IPFS snap, it started to fail with:
Pushing ipfs_v0.4.13_amd64.snap
After pushing, an attempt to release to ['edge'] will be made
Using local configuration (`.snapcraft/snapcraft.cfg`), changes will not be persisted.
Preparing to push '/home/travis/build/elopio/ipfs-snap/ipfs_v0.4.13_amd64.snap' to the store.
Received 401: '{"error_list": [{"message": "Authorization Required", "code": "macaroon-permission-required"}]}'
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.6-35b-a3b | — | — | 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. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
95
Complexity:
15
Confidence:
85
Support Request:
10
|
close stale | Report that an expired macaroon error message is unhelpful during snap push. Issue is 8+ years old with no maintainer interaction, labels, or comments. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
98
Complexity:
15
Confidence:
92
Support Request:
5
|
close stale | Unhelpful 401 error message when a snapcraft macaroon expires during CI push. Issue has zero comments, no labels, and no maintainer interaction after over 8 years. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
98
Complexity:
15
Confidence:
90
Support Request:
10
|
close stale | Report of unhelpful 401 error message when a snapcraft macaroon expires during CI push. Issue is over 8 years old with no maintainer response or comments. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
95
Complexity:
20
Confidence:
75
Support Request:
10
|
close stale | Unhelpful 401 error when a macaroon expires during snap push. The response lacks expiration details, hindering debugging. Status remains open with zero comments and over five years of inactivity, requiring triage and assignment. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #97 Confusing error message on expired macaroon | craft-store | 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. | |
| #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. | |
| #1742490 The ipfs-cluster macaroon stopped working | snapcraft (launchpad) | closed | Snapcraft push failed due to a macaroon authentication error. The issue was resolved by regenerating Travis CI credentials, restoring push access. Closed as stale. | |
| #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. | |
| #1674124 trying to push with the wrong macaroon return non user-friendly error | snapcraft (launchpad) | open | Snapcraft push with a macaroon attenuated to a different snap returns a raw 403 JSON blob instead of a user-friendly error. Opened by maintainer elopio ~9.4 years ago, zero comments, no labels beyond bitesize/store/ui, no recorded fix. |