Repository navigation
fix: retry an outdated VK Calls token - #31
Merged
luminescq merged 1 commit intoOct 5, 2026
Merged
Conversation
mrddt-tech
marked this pull request as ready for review
September 7, 2026 08:14
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
2 participants
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.
Problem
VK Calls can report
error.webrtc.auth.anonym_token.outdatedat the final join step even though the anonymous token was just issued. The previous flow then fell back to CAPTCHA handling.Root cause
The complete VK Calls token chain is short-lived and its final step can receive a stale token response.
Implementation
Retry the complete VK Calls path once only when the structured failure is from step 5 and contains that outdated-token error. The retry wait observes context cancellation. All other failures, including non-retryable call errors, retain their existing handling.
Tests
cd core && go test ./...Observed behavior
A fresh VK Calls chain can succeed after this transient final-step response with the same profile.
Trade-offs
There is at most one extra VK Calls chain, only for the narrowly identified transient error.