Supabase schema update null with self hosted install

Database & APIs

Hi there

After updating my self-hosted Supabase instance and FlutterFlow to the latest version and running "Update Schema" in FlutterFlow, all primary key id columns across every table are being incorrectly parsed. it goes from int8 to null. The actual Supabase table definition is unchanged — id is still int8 with a sequence/serial default.

Happy to provide schema export or additional debug info if helpful.

What have you tried so far?

1. Run a recent Supabase update (self-hosted or likely Supabase cloud as well)

2. Go to FlutterFlow → Supabase integration → click "Update Schema"

3. Inspect any table's id column — it now shows Data Type: String, PostgreSQL Type: null

4. Check the Issues panel — all Supabase insert actions now report missing required field id

Did you check FlutterFlow's Documentation for this topic?

Yes

3 replies