My ALL edge functions stopped running
RLSIn my supabase project, I simply used
supabase secrets set GOOGLE_API_CLIENT_ID=your-client-id
supabase secrets set GOOGLE_API_CLIENT_SECRET=your-client-secret
supabase secrets set GOOGLE_REDIRECT_URI=your-redirect-uri
supabase secrets set APP_URL=http://localhost:5173
and in my vercel:
VITE_SUPABASE_URL=https://your-project-id.supabase.co
VITE_SUPABASE_ANON_KEY=your-anon-key-here
VITE_GOOGLE_API_REDIRECT_URI=https://your-project-id.supabase.co/functions/v1/oauth-callback ( needed for separate config)
but for new deployement, all edge functions are giving me Request URL
https://ugmnrlmzvedrcwqeosoj.supabase.co/functions/v1/send-email
I think the issue is in JWT Signing Keys VS
Legacy JWT Secret
also --no-verify-jwt: to edge function solved my issue,
this error was due to I was migrating my keys from (HS256 → ECC P-256)
Help me sort this problem
supabase secrets set GOOGLE_API_CLIENT_ID=your-client-id
supabase secrets set GOOGLE_API_CLIENT_SECRET=your-client-secret
supabase secrets set GOOGLE_REDIRECT_URI=your-redirect-uri
supabase secrets set APP_URL=http://localhost:5173
and in my vercel:
VITE_SUPABASE_URL=https://your-project-id.supabase.co
VITE_SUPABASE_ANON_KEY=your-anon-key-here
Google OAuth (Frontend only - from Google Cloud Console)
VITE_GOOGLE_API_CLIENT_ID=your-google-client-id.apps.googleusercontent.comVITE_GOOGLE_API_REDIRECT_URI=https://your-project-id.supabase.co/functions/v1/oauth-callback ( needed for separate config)
but for new deployement, all edge functions are giving me Request URL
https://ugmnrlmzvedrcwqeosoj.supabase.co/functions/v1/send-email
I think the issue is in JWT Signing Keys VS
Legacy JWT Secret
also --no-verify-jwt: to edge function solved my issue,
this error was due to I was migrating my keys from (HS256 → ECC P-256)
Help me sort this problem
