Skip to content

fix: reload the folder after a silent token renewal - #4419

Merged
JammingBen merged 1 commit into
mainfrom
fix/retry-folder-load-after-token-renewal
Nov 12, 2026
Merged

JammingBen merged 1 commit into
mainfrom
fix/retry-folder-load-after-token-renewal

Conversation

@JammingBen

Copy link
Copy Markdown
Member

Description

When the server rejected an access token the client still considered valid (e.g. clock skew after wake), the token got renewed silently but the folder was never loaded again, so an existing folder showed "Resource not found" until a reload.

  • handleAuthError now resolves to whether the token got renewed.
  • The folder loader retries the load once after a successful renewal.
  • A 401 on the retry goes through the normal auth error handling again (renewal first, logout only if it fails), so a valid session isn't ended, as intended by fix: retry silent token renewal before logout on auth error #2951.

Related Issue

@JammingBen
JammingBen merged commit 998a59e into main Nov 12, 2026
29 checks passed
@JammingBen
JammingBen deleted the fix/retry-folder-load-after-token-renewal branch November 12, 2026 13:24
@openclouders openclouders mentioned this pull request Nov 12, 2026
1 task
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

An existing folder shows "Resource not found" after the server rejected the access token

2 participants