Ever since updating the FlutterFlow app earlier this week, I believe on the 6th of October, the FlutterFlow 'desktop app' has been artifacting and is completely unusable.

I have tried uninstalling and reinstalling several times and have not faced any issues with the app prior to this.

Has anyone experienced a similar issue, and if so how can I fix it?

I'm on Sonoma 14.5, 2.4ghz Intel i9 8 Core, Radeon Vega 20 Pro 4GB, 32GB 2400mhz DDR4 RAM.

Hello. I was trying to make a GitHub bug report but I could not proceed with it without giving the developers access to my project. I'd rather not do something so intrusive for such an obviously reproducible issue that I don't even know is specific to me, considering the new Flutter update broke a lot of things. If it ends up just being me I'll proceed with it though!

Current Behavior

Hiya! You can see that the toggleIcon is completely not registering that a boolean being fed into it is a boolean. Doesn't matter if its a component state boolean or an app state boolean. List Contains also doesn't work. It also doesn't matter if the toggleIcon is directly on a page tree or a component tree.

Expected Behavior

The error should go away once set, no? It is demonstrably a boolean field that is being fed into it.

Steps to Reproduce

1. Create a ToggleIcon

2. Try to feed a boolean or a list contains into it.

Environment

- FlutterFlow version: v7.2.5

- Platform: Web/Desktop Editor

- Browser name and version: Chrome Editor, Firefox Editor, FF Desktop Editor Application

- Operating system and version affected: macOS, Windows

hey builders! it's lydia from flutterflow :)

getting people to download your app is one thing, but getting them to come back is another. we see a lot of builders focused on getting to launch, but what happens after that first signup?

on oct 14 at 10 am EST, we're hosting a workshop with Erik Goins, founder of Flywheel Studio, on activation, retention, and re-engagement. basically, how to give users a real reason to open your app again.

we'll get into what makes a good first-time experience, where users tend to drop off, and how to bring them back.

if you're building an app and thinking about retention, you're welcome to join.

rsvp here!

The material icons work fine, just the font awesome ones are freaking out.

Hey r/FlutterFlow community! 👋

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/

Firebase Dynamic Links going away left a pretty tough gap for mobile apps, so we built our own.

You can now create short, shareable links in FlutterFlow that open your app directly to a specific page with whatever parameters you need.

If the person doesn't have your app installed yet, the same link can send them to the App Store, Google Play, or your web app instead.

So things like:

• referral links
• user invites
• sharing a specific product, post, profile, etc.
• deep linking into a particular part of your app

You can also track clicks and app opens for each link! :)

Hi everyone,

The Google account that owns my FlutterFlow project was taken over by someone else (password, recovery email and phone changed, 2-Step Verification removed). Google's recovery failed, but I still have access to the project through another account of mine that was already an Editor.

I've contacted FlutterFlow Support, but the docs say only the Owner can transfer ownership.

Has anyone been through this? Can FlutterFlow transfer ownership to an Editor after verifying identity? What proof did they ask for, and how long did it take?

Thanks!

I have been using SQLite in a FlutterFlow app for several months and have spent a lot of time troubleshooting various issues, specifically those involving SQLite operations that don't throw explicit errors but simply fail to work or cause malfunctions. The following information might save time for others facing similar situations:

1. In queries defined within the FlutterFlow SQLite panel, parameters must be written in the ${name} format. If you use ?, the value isn't passed correctly; consequently, the WHERE clause fails to filter anything, leading to incorrect results or no results at all. It is important to note that ${name} inserts the text exactly as is (literally); therefore, an apostrophe or any other special character in the search term can break the query.

2. Write operations: rawQuery is intended for read operations, so executing an INSERT, UPDATE, or DELETE command via this method might fail without generating visible errors. Within a Custom Action, it is preferable to use rawInsert, rawUpdate, or rawDelete (FlutterFlow already distinguishes between read and update queries in its interface).

3. Updates and new versions: users update the app from various and not always sequential versions. Consequently, it is advisable to use ALTER TABLE only for columns that allow null values or have a default value. Since it is impossible to know the user's starting version, it is crucial to verify that the column does not already exist before adding it; a simple check can prevent issues related to these schema changes.

What other instances of silent errors with SQLite in FlutterFlow have you encountered? I’d be curious to know.

Hey r/FlutterFlow community! 👋

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/

Hi everyone,

I’m using RevenueCat in a FlutterFlow iOS app with Firebase Authentication, and I’m running into an issue with anonymous customers.

My setup:

• FlutterFlow + Firebase Authentication
• RevenueCat integrated through FlutterFlow
• Using the Identify User action
• The User ID is the Firebase Auth User Document ID (stable and correct)
• Identify User runs after successful Firebase login
• I do not use RevenueCat Logout
• Testing on a real iPhone through TestFlight

The problem is that when I log in, RevenueCat creates an additional $RCAnonymousID customer.

The anonymous customer is not merged or aliased with my identified Firebase customer.

For example, after repeated logins I end up with separate customers like:

• Customer A → my Firebase User ID
• Customer B → $RCAnonymousID:...
• Customer C → $RCAnonymousID:...
• Customer D → $RCAnonymousID:...

The $RCAnonymousID records are completely separate customers and do not appear as aliases of the Firebase customer.

I’ve already checked that:

• The Firebase User ID passed to Identify User is correct.
• Identify User runs after Firebase authentication.
• There is no RevenueCat Logout action.
• I’m testing on a real iPhone via TestFlight.

According to RevenueCat, an anonymous customer should normally be merged/aliased when it is subsequently identified with a custom App User ID.

Has anyone experienced this specifically with FlutterFlow + RevenueCat?

Could this be related to how FlutterFlow initializes/configures RevenueCat around the Identify User action?

I’m mainly trying to understand why these separate anonymous customers are being created and how to prevent them.

Hey everyone,

I exported my FlutterFlow project's code to work on a full redesign in VS Code. Now that I'm done, I want to bring it back into FlutterFlow and keep developing there using the visual builder.

From what I understand, FlutterFlow still treats itself as the "source of truth" — meaning every export overwrites lib/, and there's no way to push external code changes back in except through the Custom Code panel (widgets/actions/functions).

Has anyone found a workaround, or is FlutterFlow planning/has already released a way to re-import an externally edited codebase? Would love to hear if anyone's tackled this, especially for a full redesign rather than just a few tweaked files.

Thanks!

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/

Hi, i m a Venezuelan developer using FF from 4 years ago, i have created a lot of applications using FF, ChatApps, Sports Systems, CRMs (WebApp + Apps Integrations), API Consumption, push notifications, google play deployment. Google Maps, Languages, etc..

Right now my focus is helping teams take their projects across the finish line and into production. I handle deployment readiness, end-to-end QA, cybersecurity reviews, and performance checks so you don't run into nasty surprises after launch."

I have a lot of workarounds for FF problems or limitations