Skip to content

Return ClientError::MissingRefreshToken instead of panicking - #97

Merged
kilork merged 1 commit into
masterfrom
fix-93-refresh-token-panic
Oct 4, 2026
Merged

kilork merged 1 commit into
masterfrom
fix-93-refresh-token-panic

Conversation

@kilork

@kilork kilork commented Aug 30, 2026

Copy link
Copy Markdown
Owner

Fixes #93

refresh_token is provider-controlled: ensure_token refreshes an expired
token and a token response without a refresh_token made the calling
application panic. The error is raised before any network request.

Fixes #93
@kilork
kilork force-pushed the fix-93-refresh-token-panic branch from f115fff to b3fb343 Compare October 4, 2026 19:36
@kilork kilork self-assigned this Oct 4, 2026
@kilork
kilork merged commit a5fc0f5 into master Oct 4, 2026
2 checks passed
@kilork
kilork deleted the fix-93-refresh-token-panic branch October 4, 2026 19:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

refresh_token panics when refresh_token is missing

1 participant