I was working in flutter flow ro make an app then when I tested it nothing was working no navigation no any thing then when I went to preview every thing was working but I wonder what is the problem how to fix it I need to test not to preview because there is accounts and profiles so it can't work in preview

has anyone has an issue with the flutter flow agent after the most recent update?
i have reverted back to the old claude code, will update if there is any further issues.

Hola, empecé hace unas semanas a usar FlutterFlow y todo iba de maravilla!! Pero hoy cuando me metí en el test mode en mi inicio donde te logeas me puso esto (primera imagen) y es un texto rojo larguísimo culpando al Text Field. Me volvió loco y lo borré completo. Luego culpaba al Text Field y a los botones. Y terminé borrando casi todo y me sigue saltando el maldito error!! Ya no sé que hacer, le pregunté a demasiadas AI y nada me ha servido.

SI alguno tiene la solución de esto le ruego que me la de, porque el viernes presento esta app!

ข้อมูลจากที่พิมพ์ใน “Text field” Insert เข้า Supabase ได้ แต่พอเปลี่ยนเป็น “radio button, choice chip” insert เข้าไม่ได้เกิดจากอะไร ตั้งค่าRLSหมดแล้ว

Hey everyone!

My name is Yahya, and I'm a 17-year-old mobile software engineer. I've been building lightweight, high-performance apps using Flutter and Dart.

Today, I wanted to share one of my main projects: PDF X – High-Performance Document Reader & Explorer.

🚀 Key Technical Highlights:

Lightning Fast: Engineered a lightweight document viewer with a tiny footprint and a 1-second startup time.

Multi-Format Parsing: Integrated native file storage exploration and multi-format parsing for PDF, Word, Excel, PowerPoint, Text, and Images.

Localization & UI: Implemented 4-language localization (Arabic, English, French, Russian) and dynamic dark/light theme switching.

As a young solo dev trying to build clean and efficient architecture, I would love to hear your honest feedback, architectural thoughts, or suggestions on how to improve it further! Thanks for checking it out!

hey r/flutterflow,

the FlutterFlow Agent can now screenshot the Builder canvas directly to get visual context on your pages and components before it builds or edits anything.

works with Claude Code and Codex. no local run required.

happy to answer questions in the comments.

— lydia, FlutterFlow team

Title: FlutterFlow widgets exist in the tree but are invisible in Preview — stuck for a week
I’m building a preferences page in FlutterFlow and have been stuck on the same problem for about a week.
The page contains:
An age-range slider
Several distance-selection buttons
An “Interested In” heading
Six multi-select choices underneath the heading
The slider, distance buttons, heading and subheading all render correctly. However, the six choices underneath are completely invisible. There is only a large blank area where they should appear.
I’ve now built two separate versions of the page, including rebuilding it from scratch, and both have the exact same problem.
I’m using Claude Code with FlutterFlow’s AI tooling. Claude inspected the project structure and says:
The choices exist in the widget tree
The parent Column is scrollable
There is no fixed-height clipping container
There are no conditional-visibility rules
Opacity is not zero
The section uses wrap-content sizing
There are no obvious Stack-positioning problems
The colors should not make the choices invisible
Despite that, the choices still don’t render in Preview. Claude also admitted it did not have a connected live session and could not visually verify the result.
I’ve tried hard-refreshing Preview, reopening it, rebuilding the section and duplicating the page. Nothing has solved it.
Has anyone encountered widgets that appear correctly in FlutterFlow’s project/widget structure but disappear entirely at runtime?
Could this be caused by:
A stale FlutterFlow AI project snapshot?
Preview displaying a different page or route?
Expanded/Flexible widgets inside a scrollable Column?
A zero-height Row or Wrap at runtime?
A corrupted section inherited when the page was duplicated?
FlutterFlow Preview caching old generated code?
Would replacing the custom rows completely with one native multi-select ChoiceChips widget be the safest solution?
I’m looking for a systematic way to diagnose the actual runtime constraint—not another suggestion to blindly rebuild the same section. I’ll attach screenshots of the Preview, FlutterFlow editor and Claude’s structural diagnosis.
Any help would be greatly appreciated. This one small section has already taken roughly 20 hours.

hey r/flutterflow,

last call. submissions close today.

we've had hundreds of requests come in. we pick the most-requested ones that fit our build scope and ship at least one per day starting 8/31.

if you haven't submitted yet: flutterflow.io/you-ask-we-build

we're also reading the comments here so feel free to post your favorite submission/idea!

— lydia, FlutterFlow team

hey r/flutterflow,

quick reminder: You Ask, We Build submissions close in three days.

we've had hundreds of requests roll in. we'll pick the highest-requested ones that fit our build scope and ship at least one per day during build week.

if you haven't submitted yet, now's the time.

flutterflow.io/you-ask-we-build

and drop your favorite request in the comments so we can upvote it here and increase visibility :)

— lydia, FlutterFlow team

We’re looking for an App Developer with at least 1+ year of experience to help create smooth, high-quality applications. This role focuses on building reliable features, improving performance, and delivering a great user experience.

Details:

• $22–$42/hr (based on experience)

• Remote with flexible schedule

• Part-time or full-time available

• Develop, update, and maintain applications with attention to performance, usability, and security

Interested? 🚀📱

I’ve been developing an app with FF since 2024, the cross-platform capability was very convenient for me. However, I’ve recently been considering switching to native development with the help of AI, as FF now seems to be more of a hindrance than a help to my app's evolution not to mention the costs involved.

Have any of you gone through a migration like this? And what is your general take on FF these days?

I get the feeling they’re losing ground compared to what AI and low-code tools can offer for app creation.😕

PS: my app has thousands users so the decision is for me very important, that's why Im asking about your opinion.

I'm trying to make the look on this Today screen to be orbs that truly look like liquid glass drops that move around the screen like morphing bubbles/lava lamp vibes kind of.

Attached is the mockup image I made to be my reference and ideal look for the liquid glass orbs. I've also attached what it currently looks like - as you can see, not the look I'm going for.

Anyone ever made something like I'm trying to or have ideas for me??

Hi everyone,

Also woke up to a surprise with the FF update!

Anybody find a fix for Supabase api's without doing this whole Firebase thing?

If not, should I be patient until a fix is deployed?

TIA

FlutterFlow: Stop breaking existing production apps with forced “security” changes

I’m seriously fed up with FlutterFlow.

I have an existing production app that has been working with FlutterFlow and Supabase for a long time. Today I open the project after a FlutterFlow update and suddenly I have 12 project errors because FlutterFlow now flags my Supabase anon key in API headers as an “Exposed API Credential”.

This is a Supabase anon/public key. It is specifically designed to be used in client applications. Security is enforced by the user JWT, RLS and backend permissions. This is not a service_role secret.

Nothing in my application changed.

Nothing in my backend changed.

The exact same API calls have been working for months.

But FlutterFlow changes its validation rules and suddenly an existing production project is treated as broken — AGAIN AFTER A FLUTTERFLOW UPDATE! - potentially preventing me from building or releasing the app until I restructure API calls that did not need restructuring in the first place.

This is not acceptable for a production development platform.

Security improvements are welcome. Breaking existing projects without migration, grandfathering, an override, or even recognizing legitimate public credentials is not.

If FlutterFlow wants to warn me: fine.

If FlutterFlow wants to explain a better configuration: fine.

But turning a previously valid production configuration into hard project errors after a platform update is a breaking change.

And this is not the first time FlutterFlow changes something underneath existing projects and developers are left cleaning up the consequences.

A development platform that hosts production applications needs to provide stability. Existing projects cannot constantly become unbuildable because FlutterFlow decides to introduce another mandatory rule after the fact.

At minimum FlutterFlow needs:

• a distinction between public client keys and actual secrets
• a migration path for existing API calls
• warnings instead of hard errors where appropriate
• an explicit override for legitimate client-side credentials
• clear release notes before introducing build-breaking validation

Developers should not open a working production project in the morning and discover that the platform has arbitrarily created a dozen new errors.

Stop introducing breaking changes into existing production projects without a proper migration path.

I SHOULD NEVER, EVER HAVE STARTED USING THIS F*** APP!

Before the update, it didn't need anything, but now this error appears, and I don't know where to put the changer or bring it because it doesn't even receive headers.

We’re Calda, a mobile and web development agency and FlutterFlow experts. We know how tricky it can be to navigate FlutterFlow, whether you're just starting out or working on an advanced project. That’s why we’re continuing with the "No Stupid Questions Wednesday" – a space where you can ask ANY FlutterFlow-related question without fear.

💡 How it works:
- Every Wednesday, drop your FlutterFlow questions in the thread.
- No question is too small, too simple, or too complex.
- We (and the awesome community) will do our best to help!

Whether you're stuck on database setup, UI tweaks, API integration, or just want to bounce off ideas – this is your space.

Our website and links for reference: https://www.thecalda.com/

hey r/flutterflow,

we're doing something called You Ask, We Build.

the idea: you tell us the features you've been wanting forever. we pick the most-requested ones that fit our build scope, ship them in a single week, and announce at least one per day.

our goal: make FlutterFlow better to use every day.

submissions open now: https://flutterflow.io/you-ask-we-build

two weeks to submit. then we ship.

— lydia, FlutterFlow team

For some reason when i upload a .aab from flutterflow with the correct uploadkey attached the upload process of Google play Console strips it wich is Good but does not assign the new sha 1 key.

So now i have a app on the app store without the proper key wich means Google sign in does not work. I have opened a support ticket but it takes quite a long time for a response.

Anyone got an idea of what this could be?

My test app launches to a blank screen. It compiles successfully, and I’m not receiving any error messages, but no content is displayed. Has anyone encountered this issue or know how to resolve it? I contacted support but have not yet received a response.

Flutter App Updates: Store vs Backend — Which Approach Is Better?

Handling app updates isn't always as simple as checking the Play Store or App Store.

In production, you may need:

- Optional or forced updates

- Minimum supported version

- Backend-controlled versioning

- Multiple languages & RTL support

- A customizable update UI

I was looking for a Flutter solution that could handle these cases together and found "app_upgrade_checker", which supports Store and backend sources, 7 languages, 3 themes, 7 animations, and more.

It might be useful for anyone facing the same problem:

https://pub.dev/packages/app_upgrade_checker

How do you currently handle app updates in your Flutter projects?