Repository navigation
fix(coinpay): log why a CoinPay code exchange failed - #43
Merged
Merged
Conversation
The callback swallowed the error, so a token endpoint rejecting the client (invalid_client after the CoinPay client stopped allowing secretless PKCE) showed only 'CoinPay could not be connected' with nothing in the logs. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The CoinPay callback swallowed the exchange error, so
/app/account?coinpay=failedleft nothing in the logs. Now logs the token endpoint's status and OAuth error.Root cause of the live failure was on the CoinPay side (client
cp_924ea061…was confidential/non-legacy while tleehealth does public PKCE); fixed there by registering it as a public PKCE client.🤖 Generated with Claude Code