Description
Bug report
- I confirm this is a bug with Supabase, not with my own application.
- I confirm I have searched the Docs, GitHub Discussions, and Discord.
Describe the bug
I am developing an application with Supabase. I am currently the only user and only making at most 100 requests per day while I am testing. I have around 5 listeners for Postgres changes. However, on December 4 my Realtime egress was 3.5GB
Which does not make any sense. So I looked into the realtime logs and I am seeing a log that is being created around 66 times a minute (sometimes even 300x per minute):
"InvalidJWTToken: Invalid value for JWT claim "exp" with value 1733433091"
After some research it seems to be coming from this file: src/RealtimeClient.ts
I have the feeling this is causing my super high realtime egress usage. I have not run into this before in my other Supabase applications. I am using the JS client in the browser exactly as instructed in the documentation. Everything is working fine but this behavior is causing us running into limits.
Would love to get any pointers why this is happening.
System information
- Version of supabase-js: https://esm.sh/@supabase/supabase-js@2.46.1
- Version of Node.js: N.A. (usage in browser)