snapcraft 2.39.2 failed to release a snap: snapcraft.storeapi.errors.StoreReleaseError: <exception str() failed>
Metadata
Current evaluation
Root cause was Mozilla-side (passing a string instead of a list of channels to _store.push); Snapcraft's unprintable StoreReleaseError was fixed by commit ef350b47 and PR #2056 (merged as 1f90b2a9), shipped in 2.41.
Resolution: closed resolved
Reason: cjwatson fixed the bad exception formatting in commit ef350b470273c0fa603f5fc766bf1efee366b3ba and completed the work in PR #2056, merged as 1f90b2a91, with improved store errors on production and the Snapcraft fix released in 2.41. The reporter (johanlorenzo) confirmed the underlying pushsnapscript bug was fixed on Mozilla's end (Bugzilla 1451667), and the bug was closed after being repurposed for the remaining bad exception formatting cases.
Evaluated by: mr-cal-bot
No scores available.
Issue body
[ Originally filed as https://bugzilla.mozilla.org/show_bug.cgi?id=1451667 ]
I didn't manage to release an uploaded version of snap. I called that python function https://github.com/snapcore/snapcraft/blob/2.39.2/snapcraft/_store.py#L461 with the right path and "beta"[1]. The push phase succeeded[3], but the release one failed with[3]:
> snapcraft.storeapi.errors.StoreReleaseError: <exception str() failed>
Last time I saw the same error was when we were using snapcraft 2.25. It was about a month ago. Back then, Ken VanDine told me to upgrade to the latest version, which solved it.
Please let me know if you need more information.
[1] https://tools.taskcluster.net/groups/GYT_nZNyQzGn7wjcwBTajw/tasks/fFIauoJaQQCFAYJVeQqheg/runs/0/logs/public%2Flogs%2Flive_backing.log#L6
[2] https://tools.taskcluster.net/groups/GYT_nZNyQzGn7wjcwBTajw/tasks/fFIauoJaQQCFAYJVeQqheg/runs/0/logs/public%2Flogs%2Flive_backing.log#L858
[3] https://tools.taskcluster.net/groups/GYT_nZNyQzGn7wjcwBTajw/tasks/fFIauoJaQQCFAYJVeQqheg/runs/0/logs/public%2Flogs%2Flive_backing.log#L892
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha | — | closed resolved | Root cause was Mozilla-side (passing a string instead of a list of channels to _store.push); Snapcraft's unprintable StoreReleaseError was fixed by commit ef350b47 and PR #2056 (merged as 1f90b2a9), shipped in 2.41. | |
| stealth/space-bunny-alpha | — | closed resolved | StoreReleaseError printed '<exception str() failed>' because snapcraft's error formatting broke on certain store responses. Fixed by commit ef350b47, released in snapcraft 2.41; store-side root cause was Mozilla passing a string instead of a channel list. | |
| stealth/space-bunny-alpha | — | closed stale | Snapcraft 2.39.2’s StoreReleaseError report was closed without a documented fix, discussion, or follow-up after 17 days of inactivity. | |
| qwen/qwen3.6-35b-a3b | — | — | Abandoned. The reporter encountered a StoreReleaseError during snap release but provided no follow-up. The issue was closed without resolution. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed without resolution. The report details a StoreReleaseError during snapcraft 2.39.2 release attempts. With zero maintainer comments and significant age, the issue was likely abandoned. No fix or workaround was provided. | |
| qwen/qwen3.6-35b-a3b | — | — | Abandoned and closed due to inactivity. The StoreReleaseError with an unhelpful exception message during snap release was never addressed. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Closed without code changes or comments. The reporter indicated prior similar errors were resolved by upgrading snapcraft, suggesting a self-resolved or abandoned issue with no repository fix. |
Update history
| Date | Change |
|---|---|
| created |
Related work
-
Likely Fixed By:
canonical/snapcraft#2056
(confidence 95%)
PR 'Fix formatting of some store errors' by cjwatson, merged as commit 1f90b2a91, references LP: #1761488.
-
Likely Fixed By:
snapcraft (launchpad)#1761127
(confidence 70%)
Referenced by the reporter as a related snapcraft bug filed alongside this one (could not be retrieved in this environment).
-
Caused By:
snapcraft (launchpad)#1761488
(confidence 60%)
The malformed request came from calling _store.push() with a single channel string instead of a list, a caller-side bug in Mozilla's pushsnapscript.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1627865 Snapcraft errors when releasing a snap | snapcraft (launchpad) | closed | Resolved by improving snapcraft's error handling to check HTTP status codes before JSON decoding, alongside a fix for the underlying store race condition (bug #1610948). | |
| #1664704 snapcraft release gives misleading error when revision does not exist | snapcraft (launchpad) | open | The legacy snapcraft release error wrongly advised registering an already-registered snap; that obsolete code path was removed in ffb164b7a, and current releases use craft-store. | |
| #1967722 snapcraft upload --release fails for registered snap | snapcraft (launchpad) | closed | Upload succeeded after store registration/account access was confirmed; no Snapcraft code change was needed. | |
| #1763721 snapcraft status crashing "TypeError: Can't convert 'NoneType' object to str implicitly" | snapcraft (launchpad) | closed | Store cleanup removed the conflicting name-dispute record, and snapcore/snapcraft#2115 (12828eba2) added a missing-snap-ID guard for snapcraft status. | |
| #1691597 snapcraft push fails to a registered name | snapcraft (launchpad) | closed | Merged PR #2749 (commit ac2d48293) improved store error handling with StoreErrorList and clearer StorePushError output for forbidden and missing resources. | |
| #311 Release for 2.2 | snapcraft | merged | Snapcraft 2.2 release PR #311 was merged via 91b31e43f, with release commit 4aa6d4cb1 updating the project version to 2.2. |