Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

parity(auth): getClaims() should return typed AuthInvalidJwtError for expired JWT [from supabase-js]

Closed
  • Is something wrong?
#262 0 comments 0 reactions 1 assignee View on GitHub

Maintainers usually reply within 1 day

@Tr00d is already working on this.

Since Jul 1, 2026.

Assessment

This issue has not been assessed yet.

Description

parity

[!WARNING]
Auto-generated parity issue — may be a false positive.

This issue was created automatically by /sync-sdk-parity from a heuristic analysis of recent supabase-js commits. The tooling has limited insight into language-specific idioms and may have:

  • misidentified a JS-only change as cross-language relevant,
  • missed an existing implementation in this SDK under a different name,
  • or proposed an API shape that doesn't fit this language's conventions.

It is the SDK author's responsibility to validate the need before implementing. If this change does not apply to this SDK, please close the issue with a short note explaining why.

SDK Parity: C# implementation needed

A bug fix was made in supabase-js auth that may apply to this repository. Please confirm applicability before starting work.

Reference Implementation (supabase-js)

  • Commit: 0dc5f80
  • PR: supabase/supabase-js#2395
  • Module: auth
  • Type: bug-fix
What Changed

getClaims() now catches expired-JWT errors and rethrows as AuthInvalidJwtError, ensuring callers receive a stable named error type.

Implementation Guidance (C#)

public class AuthInvalidJwtException : AuthException
{
    public AuthInvalidJwtException(string message) : base(message) { }
}

// GetClaims() with expired JWT:
// throw new AuthInvalidJwtException("JWT has expired");
// Callers: catch (AuthInvalidJwtException e) { ... }
Key Behaviors to Match
  • Expired JWT in GetClaims() throws a specific named exception type
  • Distinguishable from generic AuthException via type check

Acceptance Criteria

  • GetClaims() with expired JWT throws AuthInvalidJwtException
  • Distinguishable from generic AuthException
  • Test covers expired JWT case

Context

  • supabase-js version: v2.107.0
  • Related: SDK-1035 (dart), SDK-1036 (py), SDK-1037 (swift)
  • Parity tracking: Auto-generated by /sync-sdk-parity
Dominant language
C#
Stars
702
Forks
106
Avg merge
2d 21h
Merged PRs (30d)
51

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from supabase/supabase-csharp

All issues in supabase/supabase-csharp

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.