Skip to content
Open
Show file tree
Hide file tree
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
abridged files from new standlone articles and placed them in suitabl…
…e articles by properly consolidating them
  • Loading branch information
mrdavidorok committed Jul 31, 2025
commit 5fa6aa06378c75c85cfc4c557603676ded8948f7

This file was deleted.

This file was deleted.

11 changes: 11 additions & 0 deletions docs/ff-concepts/file-handling/displaying-media.md
Original file line number Diff line number Diff line change
Expand Up @@ -50,6 +50,17 @@ For more details on how assets are stored in your project, see the directory [**

You can also access media files within your app that are stored temporarily in your application. For example, if you'd like to preview an image before sending it to cloud storage, you can do so by setting the source to **Widget State -> Uploaded Local File**.

:::info[Image Uploads via WebView May Fail on Real Devices]
Image uploads inside a WebView may fail on physical devices even if they work in Run/Test mode. This happens because FlutterFlow doesn't auto-request Photo Library permissions at runtime.

To fix this:
- Enable Photo Library in Settings > Permissions.
- Add a Get Permission action to request access before uploading.
- Reinstall the app on the device after adding the permission.

If permissions aren’t granted, the upload will silently fail. Users may have to manually allow access via their device’s app settings.
:::

![dm-local-upload.avif](imgs/dm-local-upload.avif)

## AudioPlayer
Expand Down

This file was deleted.

23 changes: 23 additions & 0 deletions docs/ff-integrations/authentication/firebase-auth/auth-actions.md
Original file line number Diff line number Diff line change
Expand Up @@ -22,6 +22,29 @@ Follow the steps below to add this action:

![logout](../imgs/logout-action.png)

## Handling Invalid Login Credentials

When a user enters incorrect login credentials, FlutterFlow automatically displays a `SnackBar` with an error message. This helps users understand why their login attempt failed without needing custom logic.

![](../imgs/20250430121519975010.gif)

When the **Login Action** fails, a `SnackBar` is shown with the relevant error (e.g., “No user found” or “Wrong password”). This message appears automatically during runtime; no additional configuration is required.

:::tip
There is no need to manually add alert dialogs for failed login attempts. FlutterFlow handles `SnackBar` display automatically when authentication fails.
:::

### Customize the SnackBar (Optional)

1. Select the **Login Action** from your button or trigger.
2. In the **Actions tab**, open the **Action Output** section.
3. Use conditional logic to check the error message.
4. Display a custom `SnackBar` or navigate based on the message content.

:::note
To customize the `SnackBar` further, use the **Action Output** and attach additional logic based on the error string.
:::

## Reset Password

With Firebase Authentication, there are two ways you can allow users to reset their password in your FlutterFlow app:
Expand Down
20 changes: 20 additions & 0 deletions docs/generated-code/state-mgmt-gen-code.md
Original file line number Diff line number Diff line change
Expand Up @@ -73,6 +73,26 @@ For the **iOS** platform, it uses the [**KeyChain**](https://developer.apple.com
In the case of the **Web**, it uses the [**Web Cryptography**](https://developer.mozilla.org/en-US/docs/Web/API/Web_Crypto_API) (Web Crypto) API.
:::

## Example: Check Onboarding Completion Using App State

Use a persisted app state variable to ensure users complete onboarding before accessing certain parts of your app (e.g., home screen, checkout).

Follow the steps below:

1. **Create a Boolean Variable**
- Go to **App Settings > State Management > Persisted Values**.
- Create a boolean variable like `hasCompletedOnboarding`, default: `false`.

2. **Update After Onboarding**
- On the final onboarding screen, add an **Update Persisted Value** action to set `hasCompletedOnboarding = true`.

3. **Add Conditional Navigation**
- On the target page’s **Page Load**, add a **Conditional Action**:
- If `hasCompletedOnboarding == false` → Navigate to the onboarding page.

:::tip
Use `Local State` for session-only checks; use `Persisted` for cross-session logic.
:::

## Global State

Expand Down

This file was deleted.

23 changes: 22 additions & 1 deletion docs/intro/ff-ui/builder.md
Original file line number Diff line number Diff line change
Expand Up @@ -13,6 +13,26 @@ keywords: [App Builder, FlutterFlow, UI, Design]
On opening the project, you'll see the App Builder, which consists of four main sections:
[Navigation Menu](#navigation-menu), [Toolbar](#toolbar), [Canvas](#canvas-area), and [Properties Panel](#properties-panel).

:::warning[Editor Performance Does Not Affect App Builds]

Slow performance in the FlutterFlow editor—such as UI lag or long loading times—may occur in large projects or long sessions, but **this does not impact the performance of your final app build**.

Editor slowness is typically caused by:
- Large projects with many pages or custom functions.
- Long text blocks typed directly into the editor.
- Accumulated browser cache from extended sessions.

To improve responsiveness:
- Draft long content externally before pasting into the editor.
- Restart your browser regularly.
- Use the macOS app version for better UI performance.
- Close unused pages or widgets to free up memory.

The compiled app’s performance depends on your app logic, code efficiency, and device resources—not the speed of the editor environment.

:::


![navigation-menu.avif](imgs/navigation-menu.avif)

## Navigation Menu
Expand Down Expand Up @@ -54,4 +74,5 @@ elements on the canvas. It allows you to add [Actions](../../resources/control-f
The Properties Panel will vary slightly depending on the entity you have selected. To explore the details of each Properties Panel, click on the following:

- **[Page Properties](../../resources/ui/pages/pages-properties.md)** (when you have selected a Page)
- **[Widget Properties](../../resources/ui/widgets/widget-properties.md)** (when you have selected any widget, including built-in components)
- **[Widget Properties](../../resources/ui/widgets/widget-properties.md)** (when you have selected any widget, including built-in components)

18 changes: 18 additions & 0 deletions docs/intro/ff-ui/canvas.md
Original file line number Diff line number Diff line change
Expand Up @@ -18,6 +18,24 @@ It allows zoom level adjustments and previews in light or dark mode. It also inc

This is the canvas of the device screen where you can build the user interface. You can customize the screen by adding widgets using drag and drop from the [Widget Palette](../../intro/ff-ui/widget-palette.md) and by applying properties present in the [Properties Panel](../../intro/ff-ui/builder.md#properties-panel).

### Troubleshooting Copy-Paste Issues

If you're unable to copy and paste widgets on the Canvas, the issue may be due to clipboard permissions in your browser.

Follow these steps to enable clipboard access in Chrome:

1. Click the **lock icon** in the address bar next to `flutterflow.io`.
2. In the permissions popup, locate **Clipboard**.
3. Set clipboard access to **Allow**.
4. Refresh the page and try again.

![](../imgs/20250430121511630414.png)

:::tip
If you're using Firefox, Safari, or Edge, check that browser’s permission settings to enable clipboard access.
:::


## Show or hide Navigation Menu

From here, you can open or close the
Expand Down
41 changes: 0 additions & 41 deletions docs/intro/ff-ui/embed-a-flutterflow-web-app-in-an-iframe.md

This file was deleted.

This file was deleted.

19 changes: 19 additions & 0 deletions docs/resources/data-representation/app-state.md
Original file line number Diff line number Diff line change
Expand Up @@ -127,4 +127,23 @@ Storing large or complex data types like documents in App State could lead to **

If you need to work with such data types, it's recommended to store them in Page or Component state instead.
</p>

<summary>
Why is the data type list empty when creating an App State variable?
</summary>
<p>
If you don’t see any data types when trying to create an App State variable, it's likely because <strong>Deep Linking is disabled</strong> in your project settings.

To fix this:

1. Open your FlutterFlow project.
2. Go to <strong>Settings > App Details</strong>.
3. Scroll to the <strong>Deep Linking & Route</strong> section.
4. Enable the <strong>Deep Linking</strong> toggle.

<img src="../assets/20250430121217509964.png" alt="Enable Deep Linking" />

Once Deep Linking is enabled, the list of available data types should appear when creating or editing an App State variable.
</p>

</details>
Loading
Loading