← Back to issue list

(charmhub) Provide a better error to the user on a login attempt when already having credentials (CRAFT-1269)

View original Github issue

Metadata

Project
charmcraft
Number
#916
Type
pull request
State
merged
Author
facundobatista
Labels
—
Created
Updated
Closed

Current evaluation

Merged changes that improve Charmhub login error messaging when credentials already exist, resolving issue #833 and ticket CRAFT-1269. Approved by one reviewer with minimal code modifications.

Suggested action: —

No scores available.

Issue body

Fixes #833.

Evaluation history

Date Model Scores Action Summary
qwen/qwen3.6-35b-a3b — — Merged changes that improve Charmhub login error messaging when credentials already exist, resolving issue #833 and ticket CRAFT-1269. Approved by one reviewer with minimal code modifications.
qwen3.6-35b-a3b-mtp-q6 — — Merged fix improving Charmhub login error messaging when credentials already exist, resolving issue #833 (CRAFT-1269).
qwen3.6-35b-a3b-mtp-q6 — — Merged fix improving Charmhub login error messaging when credentials already exist. Resolves #833 and addresses CRAFT-1269 by replacing confusing prompts with clearer user feedback.

Update history

No update history recorded yet.

Related issues

Issue Project State Summary Similarity
#810 Confusing output from `charmcraft login` charmcraft closed Reported confusing charmcraft login error when credentials already exist. Team agreed to improve messaging to prompt users to logout first. Issue closed and superseded by tracking issue #833 to implement the fix.
77%
#725 craft-store error when using `charmcraft login` command charmcraft closed Closed as superseded by #833. The error triggers when charmhub credentials already exist. Maintainers acknowledged the confusing UX and planned a craft-store fix, but redirected tracking to the dedicated ticket.
71%
#672 charmcraft 1.4.0: impossible to login to charmhub charmcraft closed Closed as expected behavior. Charmcraft falls back to a non-persistent memory ring on headless systems lacking a keyring, preventing credential persistence. Maintainers advised exporting credentials via environment variables instead of implementing a code fix.
71%