❓ Is There a Way to Safely Change Supabase Branch in a FlutterFlow Project?

Hi everyone,

I'm trying to switch my FlutterFlow project’s Supabase backend from the production branch to a staging branch, and I’ve run into several issues.

❗ My Main Questions:

Is there a supported or safe way to change the Supabase project (branch) in FlutterFlow without breaking the schema or import structure?
Is there any workaround to push backend code changes (e.g. supabase.dart, table definitions) that aren’t in the “Custom Code” area?
Or should I be recreating the schema cleanly on the new branch and reimporting everything?

Thanks in advance! If anyone has done this successfully or knows how FlutterFlow handles Supabase integration under the hood when switching branches, I'd appreciate your insights.

🔧 What I Tried

Changed Supabase URL and Anon Key using FlutterFlow’s settings panel under the Supabase integration.
Then I clicked “Get Schema” — this gave me errors related to duplicated exports and type conflicts.
I tried using “Clear Schema” then “Get Schema” again — same result.
So I downloaded the project source, manually updated the Supabase credentials and fixed all the import and type errors (like duplicate SupabaseTable and missing SupabaseRow).
Locally, everything runs fine now (Flutter CLI + Supabase staging branch).
But when I try to push these changes back to FlutterFlow, it doesn’t work — FlutterFlow only accepts edits in certain custom code files, and won’t let me push anything in lib/backend/supabase/**.