fix(trackers): use the shared refresh timeout for MAL token refresh

MAL token refresh waited on the general 20s request timeout while the Trakt and MDBList refresh paths use the dedicated 15s refresh timeout, so a hung refresh held the 401 retry longer on MAL than on its siblings. Align MAL with the shared refreshTimeout.
2026-08-20 01:59:00 +02:00
parent df0d71e6f8
commit b66eec827d
1 changed files with 1 additions and 1 deletions
@@ -51,7 +51,7 @@ class MalAuthService extends OAuthProxyAuthServiceBase {
        'grant_type': 'refresh_token',
        'refresh_token': current.requireRefreshToken(TrackerService.mal),
      },
-      timeout: TrackerConstants.requestTimeout,
+      timeout: TrackerConstants.refreshTimeout,
      operation: 'MAL token refresh',
    );