Skip to content

Type error in the terminal: Received an instance of Uint8Array #4806

@ashkan-ahmadi

Description

@ashkan-ahmadi

Describe the bug
I recently upgraded my Supabase CLI to v2.75.0 and when I serve my functions, none of my existing functions run and I constantly get this error of "Invalid JWT" even though nothing has changed and I'm using the correct JWT. In the terminal, I get this error:

026-02-04T23:11:50.816329639Z Using supabase-edge-runtime-1.68.4 (compatible with Deno v1.45.2)
2026-02-04T23:11:54.112049626Z TypeError: Key for the ES256 algorithm must be of type CryptoKey. Received an instance of Uint8Array
2026-02-04T23:11:54.112124751Z     at asymmetricTypeCheck (https://deno.land/x/jose@v4.13.1/lib/check_key_type.ts:14:11)
2026-02-04T23:11:54.112127417Z     at checkKeyType (https://deno.land/x/jose@v4.13.1/lib/check_key_type.ts:39:5)
2026-02-04T23:11:54.112129167Z     at flattenedVerify (https://deno.land/x/jose@v4.13.1/jws/flattened/verify.ts:78:3)
2026-02-04T23:11:54.112130459Z     at compactVerify (https://deno.land/x/jose@v4.13.1/jws/compact/verify.ts:15:26)
2026-02-04T23:11:54.112131751Z     at Module.jwtVerify (https://deno.land/x/jose@v4.13.1/jwt/verify.ts:5:26)
2026-02-04T23:11:54.112133001Z     at verifyJWT (file:///root/index.ts:95:16)
2026-02-04T23:11:54.112134209Z     at Object.handler (file:///root/index.ts:140:34)
2026-02-04T23:11:54.112135417Z     at respond (ext:sb_core_main_js/js/http.js:197:38)
2026-02-04T23:11:54.112136626Z     at handleHttp (ext:sb_core_main_js/js/http.js:131:5)
2026-02-04T23:11:54.112137834Z     at eventLoopTick (ext:core/01_core.js:168:7)

To Reproduce
Steps to reproduce the behavior:

  1. Serve functions on Supabase local instance using Supabase CLI supabase functions serve
  2. Log into your account to get the access_token in the JWT and use that to send requests to your edge functions
  3. Review the error in the terminal

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots
If applicable, add screenshots to help explain your problem.

System information
Rerun the failing command with --create-ticket flag.

  • Ticket ID: [e.g. ab1ac733e31e4f928a4d7c8402543712]
  • Version of OS: Apple M3 Pro Mac Tahoe 26.2 (25C56)
  • Version of CLI: 2.75.0
  • Version of Docker: 4.41.2 (191736)
  • Versions of services: [output from supabase services command]
 SERVICE IMAGE          | LOCAL                  | LINKED 
------------------------|------------------------|--------
 supabase/postgres      | 17.6.1.075             | -      
 supabase/gotrue        | v2.186.0               | -      
 postgrest/postgrest    | v14.3                  | -      
 supabase/realtime      | v2.73.2                | -      
 supabase/storage-api   | v1.35.3                | -      
 supabase/edge-runtime  | v1.68.4                | -      
 supabase/studio        | 2026.01.27-sha-2a37755 | -      
 supabase/postgres-meta | v0.95.2                | -      
 supabase/logflare      | 1.30.5                 | -      
 supabase/supavisor     | 2.7.4                  | -  

Additional context
If applicable, add any other context about the problem here.

  • Version of Node.js: v24.11.0

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions