Exposing Schema

Hey everyone, I'm having a heck of a time with a schema I've created that SHOULD be exposed (see screenshot). Steps I've taken: - Enable & Save wait 30s, Disable & Save wait 30s, Enable & Save wait 30s - Upgrade Postgres version to the latest - Restarted the project (multiple times) - Enabled RLS - Applied ALL of the recommended Alter table/grant usage on schema, etc I'm really at a loss on what to do at this point. I can't get a simple curl to work: curl -s -H "apikey: $DEV_SUPABASE_SERVICE_ROLE" -H "Authorization: Bearer $DEV_SUPABASE_SERVICE_ROLE" -H "Accept-Profile: billing" "$SUPABASE_DEV_URL/rest/v1/billing.subscriptions"
{"code":"PGRST106","details":null,"hint":null,"message":"The schema must be one of the following: public, ref, mkt, analytics, ingest, cfg"}% (and yes, I've validated those environment variables by doing the same thing with a different exposed schema, and I've tried it using Content-Profile with Accept-Profile, without Accept-Profile, and any other combination I can think of)
No description
0 Replies
No replies yetBe the first to reply to this messageJoin

Did you find this page helpful?