I have a DocumentBuilder page with custom TextField components (FormQuestionChild, FormQuestionChild2) that wrap a custom TextField component which wraps a native Input widget.

I need the typed values to be stored in App State variables (coreProblem, targetAudience) so that when the Generate button is tapped, those values are passed as a prompt to the Claude API via a Backend Call action.

The API works correctly in test. The action chain on Generate reads the prompt from a Text Combination of coreProblem + targetAudience App State variables. But these variables are always empty when Generate is tapped because the TextFields never save their values to App State.

The TextField component has an onChange String parameter but it's not a real callback — it doesn't trigger any action when the user types.

Question: What is the correct way to read the typed value from a custom TextField component and save it to App State either on change or at the moment a button is tapped?

FlutterFlow version: latest. No Firebase — direct API call.

I just noticed that it’s no longer possible to connect Supabase to FlutterFlow using API keys, so I tried migrating my project to the new “Connect with Supabase” method using the Supabase host.

The connection itself seems to work: my project is correctly connected to Supabase.

However, after the migration, most of my existing Supabase-related actions are no longer linked properly. I now have 162 errors across the project, mainly related to Database Actions in FlutterFlow.

It looks like a large part of my previous Supabase actions lost their connection/reference during the migration.

Has this already happened to anyone?
What is the recommended way to fix this issue without manually rebuilding all the database actions?

At the moment, I’m blocked and I’m not sure how to proceed.

Thanks in advance for your help.

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.

We are building a smart home system using FlutterFlow + Firebase + ESP32.

Currently, when we press a button/switch inside FlutterFlow, Firebase does not update consistently. In Firebase Console, writes sometimes remain 0 and the value does not change.

Our goal is:

• real-time light control

• instant state updates

• ESP32 synchronization

We want the button to instantly update Firebase and trigger devices in real time.

We are not sure whether the issue is:

• incorrect action setup

• wrong Firestore path

• Firebase rules/permissions

• realtime binding issue

• or incorrect database choice

We would really appreciate guidance on:

• how to debug this properly

• best architecture for IoT/smart home apps

• Firestore vs Realtime Database for low latency systems

Thanks.

I don't know if this is a problem specific to me or if there is indeed an issue in recent versions of the desktop application. I have been waiting for a new update, but the problem persists.

The operating system's security layer prevents the update from installing starting with 6.6.103, also today in 6.6.104

Eilidh Southren

Manoranjan Padhy

Further investigation revealed that the certificate used by Flutterflow has been revoked.

*Note that this issue does not occur when installing earlier versions.

**This also occurs when downloading the latest version from the official Flutterflow website.

What's working:

• Supabase OAuth connection completes successfully

• Schema imports cleanly (7 tables imported)

What's not working:

• App Settings → Authentication shows the warning "Supabase has not been set up yet" despite OAuth being connected

• Sign Up actions (Supabase Authentication → Create Account) do nothing when tapped in test mode

• No new user record appears in Supabase's auth.users table — the call isn't reaching Supabase at all

Questions:

1. Is Supabase Authentication fully supported on the free plan, or is there a tier requirement I'm not aware of?

2. Is there a known compatibility issue with Supabase's new Publishable/Secret API key system?

3. If neither — what step am I missing to clear the "Supabase has not been set up yet" warning when OAuth is connected?

Project: Myrios
Plan: Free
Browser: Edge on Windows 11

Thanks.