snapcraft 2.39.2 failed to release a snap: snapcraft.storeapi.errors.StoreReleaseError: <exception str() failed>
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 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.
Suggested action: —
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 |
|---|---|---|---|---|
| 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
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1967722 snapcraft upload --release fails for registered snap | snapcraft (launchpad) | closed | Abandoned and closed without resolution. The reported snapcraft upload --release failure claiming an unregistered snap despite store registration remains unresolved. | |
| #1627865 Snapcraft errors when releasing a snap | snapcraft (launchpad) | open | Snapcraft push --release hangs in 'Processing...' after a JSONDecodeError from the store status endpoint (storeapi._update_status). No maintainer activity in ~10 years; the storeapi module no longer exists in the codebase. | |
| #1499424 snapcraft throws FileExistsError: with very simple Python snap | snapcraft (launchpad) | closed | Closed without comments or explicit resolution. The FileExistsError during snapcraft stage was likely resolved in a subsequent snapcraft release or abandoned due to inactivity. | |
| #1829413 snapcraft requested file bug report | snapcraft (launchpad) | open | Snapcraft 2.43.1 crashed with FileNotFoundError on the snapcraftctl function_call fifo after a keepalived compile failure on Xenial. No maintainer activity in ~7 years; the snapcraftctl code path no longer exists in the current codebase and the affected version is EOL. | |
| #1746607 snapcraft 2.38 is very slow | snapcraft (launchpad) | closed | A performance regression in snapcraft 2.38 was abandoned and closed without resolution or comments. No fix or merge was implemented. | |
| #1743428 Exception raised when trying to operate on a snap that I don't own nor collaborate with | snapcraft (launchpad) | open | Ugly traceback (KeyError in StoreReleaseError.__str__) when snapcraft release fails due to missing package_upload permission on a snap the user does not own; reported against snapcraft 2.35, no maintainer activity in ~8.6 years. | |
| #1723965 snapcraft doesn't work | snapcraft (launchpad) | closed | Closed without resolution or comments, indicating abandonment. The reported snap command failure and GL driver errors remain unresolved. | |
| #1800119 snapcraft cleanbuild | snapcraft (launchpad) | closed | Closed without resolution. The report details a PermissionError during snapcraft cleanbuild caused by restricted access to the .aptitude directory. With zero comments and no fix applied, the issue was abandoned or marked stale. | |
| #1847912 snapcraft crashes after creating VM and querying store on macos | snapcraft (launchpad) | closed | Closed without resolution. Snapcraft 3.8 crashed on macOS with a 400 Bad Request when querying the Snap Store for core snaps during VM initialization. Likely abandoned or superseded by newer versions due to age and zero comments. | |
| #1663625 No script named 'snapcraft' | snapcraft (launchpad) | closed | A report of snapcraft failing after apt installation was closed without resolution or comments, indicating the matter was abandoned. |