Use LogWarning instead of LogError for handled OAuth failures

OAuth failures like timeout and invitation-required are expected conditions that are already displayed in the status text. Using LogError triggers SimpleErrorHandler to show an exception popup, which is redundant and distracting. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
2026-07-29 00:35:41 +00:00 · 2026-01-26 19:00:04 -08:00
2 changed files with 2 additions and 2 deletions
@@ -158,7 +158,7 @@ namespace Auth {
                // Bring game back to foreground even on failure
                WindowFocusManager.BringToForeground();

-                Debug.LogError($"[OAuthManager] Login failed: {ex.Message}");
+                Debug.LogWarning($"[OAuthManager] Login failed: {ex.Message}");
                OnLoginFailed?.Invoke(ex.Message);
                throw;
            }
@@ -499,7 +499,7 @@ public class ConnectionHandler : MonoBehaviour, ILobbySubscriber, IDisposable {
            await OAuthManager.Instance.LoginAsync(provider);
            // OnLoginSuccess or OnNewUserNeedsDisplayName will be called
        } catch (Exception ex) {
-            Debug.LogError($"OAuth login failed: {ex.Message}");
+            Debug.LogWarning($"OAuth login failed: {ex.Message}");
            if (oauthStatusText != null) { oauthStatusText.text = $"Login failed: {ex.Message}"; }
        }
    }