SDK-213 Authentication Retry logic fails with invalid JWT token #984
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.
🔹 Jira Ticket(s)
✏️ Description
When multiple network requests fail simultaneously with 401 JWT errors, only the first request gets retried after token refresh. Subsequent requests are silently dropped because their retry callbacks are not queued when a token refresh timer is already active.
Root Cause
In
AuthManager.scheduleAuthTokenRefreshTimer(), whenisTimerScheduledis true, the method returns early without storing the callback, causing it to be lost.Solution
pendingSuccessCallbacks) to store retry callbacks when timer is activescheduleAuthTokenRefreshTimerto queue callbacks instead of dropping them