Unacceptable audience in id_token" Error with Native Sign-In on Local Supabase Instance
I am using Supabase Auth with Expo.
- "@supabase/supabase-js": "^2.49.4"
- "supabase": "^2.33.9"
I'm encountering an "Unacceptable audience in id_token" error specifically with Apple and Google native sign-in, but only when running my Supabase instance locally using supabase start.
I understand that it's likely not possible to configure the Auth Providers directly in the local Supabase Studio dashboard. Is there a setting in config.toml that corresponds to the "Client IDs" configuration found in the production Supabase dashboard?
I have tried setting auth.external.[provider].client_id in config.toml to the same values used in my production dashboard (e.g., the appropriate iOS bundleIdentifier or Android client ID), but the changes don't seem to be applied.
Could there be an issue with how the configuration is being applied to the local GoTrue instance? I would like to know the correct configuration method to make native sign-in work in the local environment without issues.
- "@supabase/supabase-js": "^2.49.4"
- "supabase": "^2.33.9"
I'm encountering an "Unacceptable audience in id_token" error specifically with Apple and Google native sign-in, but only when running my Supabase instance locally using supabase start.
I understand that it's likely not possible to configure the Auth Providers directly in the local Supabase Studio dashboard. Is there a setting in config.toml that corresponds to the "Client IDs" configuration found in the production Supabase dashboard?
I have tried setting auth.external.[provider].client_id in config.toml to the same values used in my production dashboard (e.g., the appropriate iOS bundleIdentifier or Android client ID), but the changes don't seem to be applied.
Could there be an issue with how the configuration is being applied to the local GoTrue instance? I would like to know the correct configuration method to make native sign-in work in the local environment without issues.
