You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a mobile app where I listen to postgres changes with a subscription. It worked perfectly fine until some weeks ago (I have not checked this feature for some time, I don't have the precise date when it broke).
I haven't changed a line of code. Now none of my subscriptions are working. I guess something changed supabase-side, because my code is still the same.
To Reproduce
Steps to reproduce the behavior, please provide code snippets or a repository:
export const subscribeToNotificationsAPI = ( userId: string, callback: (payload: NotificationUpdate) => void ) => { supabaseClient .channel(notifications-${userId}) .on( "postgres_changes", { event: "*", schema: "public", table: "notifications", filter: user_id=eq.${userId}, }, (payload) => { console.log("nothing happens, even if I send a notification"); callback(payload as unknown as NotificationUpdate); } ) .subscribe(); };
this function is called at the root of my app inside a useEffect. I checked it was called, it is.
Expected behavior
My console log is supposed to fire when adding a row to notifications table
System information
OS: MacOS (iOS simulator, react native)
Version of supabase-js: [2.42.3]
Version of Node.js: [20]
The text was updated successfully, but these errors were encountered:
@encima Hello, thank you for your fast reply. You talking about the project and the dashboard gave me a hint about what I did wrong. The only thing that changed was my backend project, going from staging to production... and the realtime turned off on the tables !!
I turned it on again and of course everything worked fine again. I am sorry for the inconvenience and thank you for your patience 🙏
Bug report
Describe the bug
I have a mobile app where I listen to postgres changes with a subscription. It worked perfectly fine until some weeks ago (I have not checked this feature for some time, I don't have the precise date when it broke).
I haven't changed a line of code. Now none of my subscriptions are working. I guess something changed supabase-side, because my code is still the same.
To Reproduce
Steps to reproduce the behavior, please provide code snippets or a repository:
export const subscribeToNotificationsAPI = ( userId: string, callback: (payload: NotificationUpdate) => void ) => { supabaseClient .channel(
notifications-${userId}) .on( "postgres_changes", { event: "*", schema: "public", table: "notifications", filter:
user_id=eq.${userId}, }, (payload) => { console.log("nothing happens, even if I send a notification"); callback(payload as unknown as NotificationUpdate); } ) .subscribe(); };
this function is called at the root of my app inside a useEffect. I checked it was called, it is.
Expected behavior
My console log is supposed to fire when adding a row to notifications table
System information
The text was updated successfully, but these errors were encountered: