Supabase schema update null with self hosted install

[Webtica]

Can we access your project?

• I give permission for members of the FlutterFlow team to access and test my project for the sole purpose of investigating this issue.

Current Behavior

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.

Expected Behavior

Update schema and output the correct tables and data.

Steps to Reproduce

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

Reproducible from Blank

• The steps to reproduce above start from a blank project.

Bug Report Code (Required)

ITEelcn1z4ZOj7xG7c/+YMIwvwMwJ0QlUIInj+0bWRMhfKr1EJl+PMjCXFZLYtSldFdIImL9mToGpuzphoXlCvU4NTacRt1T/4RXQRbzXnutV4y1C4eaZXZ6L8NbIGqy4cC3myMkKbJoWVUt11+QfPCrG3qCf9qOYwx5e6fDbOY=

Visual documentation

See images posted here: https://community.flutterflow.io/ask-the-community/post/supabase-schema-update-null-with-self-hosted-install-IXkqe5NHVXc1Lk2?highlight=qtCo847EYi9mVaT

Environment

- FlutterFlow version: 6.6.104
- Platform: MacOS Desktop and Web
- Browser name and version: Brave 1.90.122 (Officiële build) (arm64)
- Operating system and version affected: Desktop MacOS 26.4.1
- Supabase latest may self hosted release

Additional Information

No response

[eilzo]

Hi @Webtica, thanks for flagging - taking a look now.

[Webtica]

Thanks @eilzo let me know if you need more info.

[eilzo]

Thanks @Webtica - I've recreated the issue and have a fix in progress. We should be able to deploy it within the next day.

[Webtica]

Hi @eilzo , thanks! Let me know if the update is pushed so I can test and let you know here.

[eilzo]

Will do!

[Webtica]

Hi @eilzo

I saw the latest update today but it seems to be still an issue.
Any idea when this might be fixed as this is currently blocking our workflow.

Thanks!

[eilzo]

Hi @eilzo

I saw the latest update today but it seems to be still an issue.
Any idea when this might be fixed as this is currently blocking our workflow.

Thanks!

Hi @Webtica, thanks for the update and I'm sorry to hear that. I'll take a closer look at your project. Can you confirm if you're still seeing issues 3+4 that you reported above?

[Webtica]

Hi @eilzo ,

Yes correct, see the images attached, before and after refreshing the schema.
Im on version: FF v6.6.106 Flutter 3.38.5

[eilzo]

Thanks @Webtica - I've checked and my fix wasn't included in yesterday's deployment. I'll give our deployment folks a nudge and update you here when we've pushed it. Thanks for you patience.

[Webtica]

Perfect thanks @eilzo

[Webtica]

Hi @eilzo just updated to the latest version 6.6.107 I can confirm the fix is here and working. I have been successfully updating the schema now. Thanks for the quick responses and fix!

[eilzo]

Great, you beat me to it! Glad you are sorted out, and sorry again for the disruption. Happy building!