Supabase Edge Functions unreliable for background push notifications?
edge functions821"}
Hi
I'm building a chat app using Supabase + Flutter + FCM.
Push notifications work when the app is open,
but when the app is background/closed → no notification sound and sometimes no push delivered.
Architecture:
- Supabase Realtime → Edge Function → FCM → device
- Users can receive messages WITHOUT login (public browsing app)
- So I disabled JWT verification in Edge Function
Problem:
Edge Function returns 200 OK,
FCM token exists,
but push delivery is unreliable in background.
Question:
Is Supabase Edge Functions recommended for high-scale push notifications,
or should I move the push trigger to a dedicated server (Node worker / queue)?
I want a production-grade architecture (millions users), not a temporary fix.
Any advice on the correct architec
Hi
I'm building a chat app using Supabase + Flutter + FCM.
Push notifications work when the app is open,
but when the app is background/closed → no notification sound and sometimes no push delivered.
Architecture:
- Supabase Realtime → Edge Function → FCM → device
- Users can receive messages WITHOUT login (public browsing app)
- So I disabled JWT verification in Edge Function
Problem:
Edge Function returns 200 OK,
FCM token exists,
but push delivery is unreliable in background.
Question:
Is Supabase Edge Functions recommended for high-scale push notifications,
or should I move the push trigger to a dedicated server (Node worker / queue)?
I want a production-grade architecture (millions users), not a temporary fix.
Any advice on the correct architec
