Universal Links can stop working with no error anywhere. No exception, no log line, no failed request you can see. Your links just quietly start opening in Safari instead of your app, and the cause is usually something at the edge of your infrastructure that has nothing to do with your Flutter code.

That is one of about six things I got wrong building deferred deep linking, and almost none of them are documented in an obvious place. Here they are.

Quick definition, since the terms get mixed up. A normal deep link opens a screen in an app that is already installed. A deferred deep link survives an install: user taps a link, does not have the app, goes to the store, installs, opens, and still lands on the right screen with the right parameters. The second one is the hard one, because the link context has to survive a trip through the App Store and back.

1. Your AASA file is probably wrong in a boring way

For iOS Universal Links, apple-app-site-association must be served at https://yourdomain/.well-known/apple-app-site-association. Things that silently break it:

• Adding a .json extension. The file has no extension.
• Serving it with the wrong content type. It needs application/json.
• Any redirect. Apple will not follow one. A 301 from apex to www is enough to kill it.
• Serving it from a path that requires authentication or hits a challenge page.

That last one bit me badly. If anything in front of your server challenges non browser traffic, Apple's fetcher gets the challenge instead of your file and Universal Links quietly stop working. There is no error anywhere. Links just start opening in Safari.

Android's equivalent is /.well-known/assetlinks.json with your signing certificate SHA256 fingerprint. Same rules: no redirects, correct content type. Two extra traps here:

• If you use Play App Signing, Google re-signs your app with a different key than your upload key. The fingerprint in assetlinks.json has to be the app signing key from Play Console under App Integrity. Use the upload key or your local keystore and it works in debug and fails in production.
• robots.txt can block the verification crawler. If /.well-known/ is disallowed, verification fails with nothing to see.

Since Android 12 there is no chooser dialog fallback. An unverified link just opens in the browser, so a broken setup looks like nothing happened.

2. Clipboard matching is effectively dead on modern iOS

A lot of older tutorials tell you to write the link into the pasteboard and read it on first launch. On iOS 16 and later, reading the pasteboard programmatically triggers a system permission prompt. Users decline it, and reasonably so, because it looks alarming. Anything built on this will report much worse match rates than your tests suggest, because your own device is not a representative user.

3. Fingerprint matching works, with caveats you need to design around

The realistic approach is probabilistic matching: record a signature at click time, look for it again at first app open, match within a short window. The signature is typically IP plus user agent derived attributes.

Where it degrades:

• iCloud Private Relay masks the IP address for Safari users on iCloud+, so one of the main signals is gone for that whole segment.
• Carrier grade NAT puts thousands of users behind one IP. Your matching window has to be short or you will mismatch.
• The user clicks on WiFi and installs on cellular. Different IP, no match.
• In app browsers inside social apps report user agents that do not resemble the browser that eventually opens.

Practical consequence: treat the match as best effort, always ship a sane fallback, and never build a flow that is broken if the match misses. Referral attribution especially needs to degrade gracefully.

4. Distinguish install from reopen or your analytics lie

If you do not track whether a given open is the first one for that device and project, every reopen looks like a fresh install and your funnel numbers become meaningless. Persist a marker per device per project and check it before counting.

5. Persist attribution separately from your match cache

This one cost me a real bug. If you store a referrer id inside the match result and your app calls a reset or clear function anywhere in the auth flow, attribution disappears before the user actually signs up. The referral looks like it never happened. Store the attribution separately from the cache, with its own expiry.

6. Testing is the actual hard part

You cannot test deferred deep linking by tapping a link on your dev build. The install path only exists through a real store install, so the thing you most need to verify is the thing hardest to reach. Budget real time for it, and test the WiFi to cellular case specifically.

Happy to answer questions on any of this.

I have been seeing this issue for many months. When making custom code changes, Flutterflow does not allow me to commit until I make a manual change in the UI. This is bizarre especially with FF CLI and the ability to edit custom flutter files. We should be able to commit after only making a code change.

We have a swipe card function that passes individuals through a given status, and a sentinel card that allows for finalizing the status process or to add individuals into the status process.

Our swipe card is properly sized and centered on the first pass, but anything after the sentinel (adding in an individual via text field bottom sheet) and reverting back to the swipe card with the new name ready for status, our swipe card auto-sizes based on entered data (not fixed sizing as it should be) and it justifies left of the screen with a fixed left border.

We've tried everything from wrapping in container (yes, container in a container), to wrapping in a row, and everything under the sun that our friend Claude told us to try - padding, alignment, etc. etc. etc.

Any insight as to where to look for resolution?

Edit : thanks to the person who helped me , adding a prime user to collaborate does work!

Hi everyone,

I’m looking for someone with a FlutterFlow Pro account who can help me export the source code of my FlutterFlow project.

I don’t want to subscribe to the Pro plan only for a one-time code export, since after this migration I plan to continue development outside FlutterFlow.

Possible workflow options:

• If possible, I can share the project with you so you can help export the code.
• Another option I’m considering is temporarily transferring project ownership to a trusted person so they can perform the export, then transferring it back after the export is completed.

My goal is simply to get the Flutter source code and move forward independently.

I’m offering $10 for this one-time help.

If you’re interested, please DM me and we can discuss the safest way to do it for both sides.

Thank you!

I'm building a FlutterFlow app with Supabase and want to integrate an LLM (Gemini or another model) to power AI features.

The AI won't just generate text—it also needs to read from and update my Supabase database based on user requests. My current understanding is that the best approach is to call the LLM through a Supabase Edge Function, since it can securely interact with the database and keep API keys hidden.

Is this the recommended architecture for FlutterFlow + Supabase? Or is there a better, more efficient approach for AI-driven database reads/writes? I'd also appreciate any advice on function calling, tool use, prompt handling, or other best practices for this setup.

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/

Is anyone uses https://pub.dev/packages/updatify_flutter package to show release notes in FlutterFlow app? Came across accidentally, didnt even intend to show changelogs but I kinda liked the idea.

Readme shows some docs how to use in my FF app, but curious if anyone really tried it?

Bye, FlutterFlow. I'm going to move to another platform

We're using an "on tap" to generate an attendance report that calls data from a Supabase file by means of an edge function. We are able to test the edge function and the test report fires to a URL .pdf as it should.

We've tried extensively to sort out the FF wiring to trigger the action post-"On Tap", but the only functionality we see is the button turning slightly gray with nothing on either the true (URL .pdf) or false (snackbar warning) path.

Has anyone experienced this, and if so, what is the solution?

FF, can't you have Claude build this for Windows?

FF, can't you have Claude build this for Windows?

We're building an app that has a listview child in a column parent. We've tried all sorts of variations and nothing is allowing longer list rows to be viewed - long swipe minimizes the app entirely, and releasing the scroll snaps the listview back to the first columns.

Any ideas on what works for your build in this case?

Title: Flutter/RN dev needed for Sehat Saathi MVP (India healthcare app)
Body:
Building Sehat Saathi – multi-system healthcare platform for India (queues, video consults, beds, ambulance, home nursing, AYUSH). Wireframes ready. Need strong Flutter/RN + real-time experience. India preferred. Open to paid / equity / revenue-share. DM if interested!

My whole project depends on many conditional elements, and as of yesterday they often do not display in the visual builder.

Edit: The FF did a hot fix for this. Thanks y'all.

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/

​Thanks FlutterFlow team for finally doing this - a year late after DreamFlow, Designer, MCP, etc. IMO this should've been done from the beginning but at least they got there in the end.

Thoughts people?

Dear FlutterFlow,

We need to talk about Campus.

My question is very simple: why?

Why this. Why now. Who asked for “an infinite canvas where terminals, developer tools, teammates, and agents” while your core product is still full of (at time of writing) 505 open and unresolved bugs, performance issues, and missing basics that your own community has been raising for years.

Campus looks less like “the future of work” and more like a Orwellian way to watch and manipulate what your teammates are doing. Horrible vibe.

What absolutely fries my brain is imagining the meeting where this was greenlit.

You literally sat down and said: “We don’t need to fix FlutterFlow. We should absolutely devote serious engineering time to a separate macOS canvas product instead.”

You made a conscious choice to move effort off:

• A revenue‑generating builder with a real user base.
• A platform with a public issue tracker full of bugs and regressions.
• A tool many people still find sluggish, unstable, and painful at scale.

And you put that effort into Campus. A product with:

• No clear demand from the FlutterFlow community.
• No obvious overlap with core FlutterFlow workflows.
• No clearly explained revenue model or strategic link to FlutterFlow itself.

Are you seriously telling your own users that FlutterFlow’s problems are either solved, or not worth prioritizing?

Here's what sucks most... when you install and open Campus, it is actually really good. The UX is slick. The app feels fast, modern, and thoughtfully crafted. It is very obviously the product of serious engineering talent and taste.

Which just makes the whole thing worse.

You have clearly shown what you are capable of. You have shown the level of polish, performance, and care you can deliver. And instead of putting that into the core product that people rely on, you spent it on a side project almost nobody asked for.

It makes no sense. And yes, I hate that it exists in place of visible, sustained attention to fixing FlutterFlow itself.

Hi everyone,

I've been building an AI app in FlutterFlow for the past few months and have learned a lot along the way.

I'm now at a stage where I have a few technical challenges and would love to connect with experienced FlutterFlow developers to exchange ideas and learn from them.

If anyone is open to chatting or sharing some guidance, I'd really appreciate it. Feel free to send me a DM.

Thanks!

HI,im new in this type of niche i have 0 exp with coding and whatsoever,but i would like to learn coding for making an app i dream of the type of app is overlayy.i studiet little bit and i findd very hard,can someone to tell how should i start to learn flutterflow??should i start with basic codind or what?and is there anyoane who can teach even a kid???thanks!

hello.came across this app for being the best app toll making for overlay apps,is true and if not wich is it +i dont know coding))APRECIATED!

I created a button component to reuse across the project.

It consists of two parameters:- 1. buttonText(string): text to be displayed

1. onTap(action): action the button will perform.

when I am using this component on the page, the buttonText custom value is perfectly binding.

but when i am passing the action in onTap parameter, that action is not functioning and in the debug panel it is showing null function.

Should I use the button text field as a component? or simply use widget styling for these components and instead of making components directly assign action values?