Merge branch 'refs/heads/main' into update-misc

Author: PoojaB26

docs/ff-concepts/adding-customization/custom-code.md

@@ -14,7 +14,7 @@ While FlutterFlow provides a wide range of pre-built components and functionalit
 times when you need to extend your app with custom logic or UI components that are not available out of the box.
 This is where writing custom code comes into play. 
 
-There are a few different ways to make custom code accessible in FlutterFLow:
+There are a few different ways to make custom code accessible in FlutterFlow:
 
 * **[Custom Functions](custom-functions.md):** Custom Dart functions that can be used to set Widget or Action properties. 
 * **[Custom Actions](custom-actions.md):** Custom Dart functions that can be triggered by [Action Triggers](https://docs.flutterflow.io/resources/functions/action-triggers/) or used as nodes in an [Action Flow](https://docs.flutterflow.io/resources/functions/action-flow-editor#action-flow-editor). These are usually `async` functions and are able to import [custom package dependencies](#adding-a-pubspec-dependency).
@@ -522,4 +522,4 @@ If any project errors related to packages arise, they will be displayed in both
         allow="clipboard-write">
     </iframe>
 </div>
-<p></p>
+<p></p>

docs/ff-concepts/design-system/design-system.md

@@ -731,7 +731,7 @@ Make sure you have the proper rights or licenses to use the icons in your applic
 
 **Steps to Generate and Add Custom Icons**
 
-1. Head over to the [iconmoon](https://icomoon.io/app/#/select).
+1. Head over to the [IcoMoon](https://icomoon.io/app/#/select).
 2. Import your custom icon (.svg) or select from the free icons set.
 3. Select the **Generate Font** tab.
 4. Click on the Settings button (gear icon) beside the download text on the bottom right side.
@@ -836,7 +836,7 @@ If you prefer watching a video tutorial, here is the guide for you:
 
 Creating a theme for widgets ensures that your app looks consistent and has a cohesive design. The Theme widgets can be reused, making it easy to update the styles of your app. If you decide to change any property of the widget, such as color scheme or fonts, you can update the theme widget instead of going through every widget individually. This can save a lot of time and effort, especially in larger projects.
 
-For example, creating theme widgets for different types of buttons such as 'primary_button', 'secondary_button', and 'tertairy_button' with specific attributes like width, color, icon, border radius, and padding. Then, these widgets can be directly added to a page or applied to an existing widget.
+For example, creating theme widgets for different types of buttons such as 'primary_button', 'secondary_button', and 'tertiary_button' with specific attributes like width, color, icon, border radius, and padding. Then, these widgets can be directly added to a page or applied to an existing widget.
 
 ### Adding theme widgets
 
@@ -1000,4 +1000,4 @@ If you prefer watching a video tutorial, here's the one for you:
 <details>
 <summary>How is the theme widget different from creating a template and component?</summary>
 <p>The Theme Widget allows you to customize the visual appearance of a single widget, whereas templates consist of multiple widgets that create a unique UI layout with a specific purpose. On the other hand, components are fully-featured custom widgets that combine multiple widgets and actions to complete a task.</p>
-</details>
+</details>

docs/ff-concepts/navigation-routing/deep-dynamic-linking.md

@@ -847,6 +847,9 @@ Use the link data from this callback to:
 - Load content from Firestore using a referenced ID.
 
 
+:::danger[Testing Deeplinks]
+It’s recommended to test deep links on a **physical device**, as link verification (especially for Universal Links or App Links) may not consistently work on emulators or simulators.
+:::
 
 
 

docs/ff-concepts/navigation-routing/nav-overview.md

@@ -63,12 +63,12 @@ This action involves navigating to a new screen by pushing a new route onto the
 
 **What Happens Under the Hood:**
 
-- When you push a route, a new screen is placed on top of the current stack. This means the current screen is still in the stack but is not visible to the user.
+- When you push a route, a new screen is placed on top of the current stack. This means the previous screen is still in the stack but is not visible to the user.
 - The new screen becomes the active screen that the user interacts with.
 
 :::info
 
-Learn more about adding this action [**here**](../../ff-concepts/navigation-routing/page-navigation.md#navigate-to-action).
+Learn more about adding this action in the [**page navigation guide**](../../ff-concepts/navigation-routing/page-navigation.md#navigate-to-action).
 
 :::
 
@@ -83,7 +83,7 @@ This action involves navigating back to the previous screen by popping the curre
 
 :::info
 
-Learn more about adding this action [**here**](../../ff-concepts/navigation-routing/page-navigation.md#navigate-back-action).
+Learn more about adding this action in the [**page navigation guide**](../../ff-concepts/navigation-routing/page-navigation.md#navigate-back-action).
 
 :::
 
@@ -98,6 +98,6 @@ This action involves replacing the current route with a new route. Unlike pushin
 :::info
 
 - This is useful when you want to prevent the user from navigating back to the previous screen.
-- This action is essentially the **Navigate To** action with the **Replace Route** option enabled. Learn more about adding this action [**here**](../../ff-concepts/navigation-routing/page-navigation.md#navigate-to-action).
+- This action is essentially the **Navigate To** action with the **Replace Route** option enabled. Learn more about adding this action in the [**page navigation guide**](../../ff-concepts/navigation-routing/page-navigation.md#navigate-to-action).
 
-:::
+:::

docs/ff-integrations/ai/ai-agents.md

@@ -76,14 +76,15 @@ You can obtain your OpenAI API key from [**OpenAI API Keys**](https://platform.o
 
 #### Request Options
 
-Here, you specify the type of inputs users can send to the AI.
+Define the types of inputs users can send to the AI agent. You can enable one or more of the following options:
 
-- **Text**: Allows users to send text-based messages.
-- **Image**: Enables image input, allowing the agent to analyze photos.
-- **Audio**: (Google Agent only) Allows to send audio messages or voice inputs.
-- **Video**: (Google Agent only) Allows users to send short video clips to analyze.
+- **Text**: Allows users to send written messages, questions, or prompts.
+- **Image**: Enables users to upload photos for the AI to analyze visual content, such as objects, styles, or scenes.
+- **PDF** (Anthropic and Google Agent only): Lets users submit PDF documents, allowing the AI to extract and interpret information from files like resumes, reports, or forms.
+- **Audio** (Google Agent only): Supports voice input, enabling users to record or upload audio clips for transcription, sentiment analysis, or voice-based commands.
+- **Video** (Google Agent only): Allows users to submit video files, enabling the AI to analyze visual elements.
 
-Selecting multiple input types makes it easier for users to clearly communicate what they need. Instead of relying only on text descriptions, users can combine inputs—for example, uploading an image along with text to better illustrate their queries and help the agent provide more accurate responses.
+Selecting multiple input types makes it easier for users to clearly communicate what they need. Instead of relying only on text descriptions, users can combine inputs. For instance, in an AI Stylist agent, enabling both Text and Image allows users to either describe their outfits in words or upload clothing photos for personalized analysis.
 
 #### Response Options
 

docs/ff-integrations/storage/firebase-storage/storage-library.md

@@ -0,0 +1,104 @@
+---
+slug: /integrations/firebase-storage/storage-library
+title: Firebase Storage Library
+description: The Firebase Storage Library provides access to the files in Cloud Storage through the Firebase SDK beyond what FlutterFlow's built-in support provides.
+tags: [Firebase Storage, Cloud Storage, Integration, Library]
+sidebar_position: 2
+keywords: [FlutterFlow, Firebase Storage, Cloud Storage, Integration, Security]
+---
+
+The [Firebase Storage Library][storage-library-item] provides access to the files in Cloud Storage through the Firebase SDK beyond what [FlutterFlow's built-in support](/concepts/file-handling) provides.
+
+
+[storage-library-item]: https://marketplace.flutterflow.io/item/Ec3NWw8sxqJ1tbriOIEE
+
+## Instructions
+
+To start using this library:
+
+1. [Import the library](/resources/projects/libraries/#importing-a-library) into your existing FlutterFlow project.
+2. [Connect your FlutterFlow project to Firebase](/integrations/firebase/connect-to-firebase/) (if you haven't done so already).
+   The library will default to using the default bucket of your associated Firebase project. You can override this behavior by passing an explicit bucket URL to any of the actions. 
+3. [Use the Custom Actions](/concepts/custom-code/custom-actions/#using-a-custom-action) and Custom Functions in your Action Flows.
+
+
+### Custom actions
+
+* `uploadFileToBucket` \- Upload a file to any path in any bucket that you have write access to.  
+  * **Parameters:**
+    * The `bucketName` (`String?`) to upload the file to. If you leave this empty, it uses the default bucket of the associated Firebase project.  
+    * The `fullPath` (`String?`) where the file will be written to inside the bucket. If this is specified, the `prefix` parameter is ignored.  
+    * The `uploadedFile` (`FFUploadedFile`) that is to be uploaded to Cloud Storage. This is the action output of a previous `Store media for upload` action.  
+    * The `prefix` (folder/directory) (`String?`) where the file will be uploaded to. If `fullPath` is not specified, the action uses this parameter and the `name` of the `uploadedFile` to determine the full path where it writes the file.  
+  * **Action result:**  
+    * If successful, the action result is a `fileObject` containing the full path of the uploaded file.  
+  
+* `listAllFilesInBucket` \- List all files in any bucket that you have read access to.   
+  * **Parameters:**  
+    * The `bucketName` (`String?`) to list the files from. If you leave this empty, it uses the default bucket of the associated Firebase project.  
+    * The `listType` (`StorageListType?`) of the items to list (files, directories, both). If left empty, the action will list both files and prefixes (folders/directories).  
+    * The `prefix` (`String?`) is the `/` separated path from which to list files. If left empty, the action will list the items in the root of the storage bucket.  
+  * **Action result:**  
+    * If successful, the action results in a `List` of `fileObject` elements. 
+    
+* `downloadFile` \- Download the data for a file that you have read access to. This downloads the actual data into your application code. If you instead want a public URL to the data, use `getDownloadUrl` instead.  
+  * **Parameters:**  
+    * The `bucketName` (`String?`) to download the file from. If you leave this empty, it uses the default bucket of the associated Firebase project.  
+    * The `fullPath` (`String`) of the file whose data will be read from the bucket.  
+  * **Action result:**  
+    * If successful, the action result is an `FFUploadedFile` with the data of the file that was read from the bucket.  
+    
+* `getDownloadUrl` \- Get the download URL for a file in a bucket that you have read access to. This URL then provides public, read-only access to the file  
+  * **Parameters:**  
+    * The `bucketName` (`String?`) that contains the file. If you leave this empty, it uses the default bucket of the associated Firebase project.  
+    * The `fullPath` (`String`) of the file for which to get the download URL.  
+  * **Action result:**  
+    * If successful, the action result is a HTTP URL that allows public access to the file.  
+    
+* `getMetadataForFile` \- Get the metadata for a file in any bucket that you have read access to  
+  * **Parameters:**  
+    * The `bucketName` (`String?`) that contains the file. If you leave this empty, it uses the default bucket of the associated Firebase project.  
+    * The `fullPath` (`String`) of the file for which to get the download URL.  
+  * A**ction result:**  
+    * If successful, the action result is a `FullMetadata` with all the metadata and custom metadata of the file.  
+    
+
+* `updateMetadataForFile` \-  Update the metadata for a file in any bucket that you have write access to  
+  * **Parameters:**  
+    * The `bucketName` (`String?`) that contains the file. If you leave this empty, it uses the default bucket of the associated Firebase project.  
+    * The `fullPath` (`String`) of the file for which to get the download URL.  
+    * The `metadata` (`SettableMetadata`) to write to the Cloud Storage bucket for the file. If any value is left out or empty in the metadata, it is left unmodified in Cloud Storage.  
+  * **Action result:**  
+    * If successful, the action result is a `FullMetadata` with all the metadata and custom metadata of the file after the update.  
+    
+
+* `getPathFromUrl` \- Get the path for a file based on its (https:// or gs://) URL. This is a synchronous call, as it doesn't require any call to the server.  
+  * **Parameters**  
+    * The `Url` to parse.  
+  * **Action result:**  
+    * The action result is a `fileObject` derived from the URL.  
+    
+* `deleteFileFromBucket` \- Deletes a file from any bucket you have write access to.  
+  * **Parameters:**  
+    * The `bucketName` (`String?`) that contains the file. If you leave this empty, it uses the default bucket of the associated Firebase project.  
+    * The `fullPath` (`String`) of the file to delete from the bucket.  
+  * **Action result:**  
+    * If the action succeeds the file has been deleted. There is no additional information.
+
+### Enums
+
+* `StorageListType` is an enumeration of the types of items that the `listAllFilesInBucket` action can return. Values:  
+  * `files`: List only the files in the specified path.  
+  * `prefixes`: List only the prefixes in the specified path. You might more commonly refer to these as folders or directories, but since Cloud Storage doesn't actually have support for folders/directories, it uses `/` characters in the file names to emulate those and calls them prefixes.  
+  * `filesAndPrefixes`: List both files and prefixes in the specified path.
+
+### Data Types
+
+* `fileObject` \- the metadata for a file or prefix (folder/directory) in Cloud Storage. It has the following fields:  
+  * `fullPath` (`String`) \- The full path of the file/prefix inside the storage bucket. The value does not start with a leading `/`.  
+  * `isPrefix` (`Boolean`) \- Indicates whether the object is a file (`false`) or prefix (folder/directory) (`true`).  
+
+
+* `FullMetadata` \- the full metadata of an item in a storage bucket as returned by `getMetadataForFile`, modelled after the [`FullMetadata` class in the Firebase SDK for Cloud Storage](https://pub.dev/documentation/firebase_storage/latest/firebase_storage/FullMetadata-class.html).
+* `SettableMetadata` \- the settable metadata of an item in a storage bucket, as passed to a call to `updateMetadataForFile`, modelled after the [`SettableMetadata` class in the Firebase SDK for Cloud Storage](https://pub.dev/documentation/firebase_storage/latest/firebase_storage/SettableMetadata-class.html).  
+* `KeyValuePair` \- A `String`/`String` key/value pair as used for the `customMetadata` in the `FullMetadata` and `SettableMetadata` data types.

docs/generated-code/ff-app-state.md

@@ -34,15 +34,14 @@ class FFAppState extends ChangeNotifier {
     notifyListeners();
   }
 
-   // App State variable of primitive type with a getter and setter
-    bool _enableDarkMode = false;
+  // App State variable of primitive type with a getter and setter
+  bool _enableDarkMode = false;
 
-    bool get enableDarkMode => _enableDarkMode;
+  bool get enableDarkMode => _enableDarkMode;
 
-    set enableDarkMode(bool value) {
+  set enableDarkMode(bool value) {
     _enableDarkMode = value;
-   }
-
+  }
 }
 ```
 
@@ -52,7 +51,7 @@ The `_enableDarkMode` is an App State variable created by developer that creates
 When updating an `AppState` variable from the Action Flow Editor, you will be presented with several **[update type](../resources/data-representation/app-state.md#update-type)** options such as **Rebuild All Pages**, **Rebuild Current Page**, and **No Rebuild** in the Action Settings. Let's see how the generated code changes when these options are selected.
 
 ### Rebuild Current Page
-When a developer chooses to update App State with the update type set to **Rebuild Current Page**, the corresponding `setter` is called. Immediately after, `setState((){});` is invoked, which updates only the current page. 
+When a developer chooses to update App State with the update type set to **Rebuild Current Page**, the corresponding `setter` is called. Immediately after, `setState(() {});` is invoked, which updates only the current page. 
 
 Here's an example of the generated code when we update the App State `enableDarkMode` in the `onInitialization` action trigger of the `ProductListPage`.
 
@@ -90,7 +89,7 @@ Only the setter is called with no setState or update method invoked afterward. T
 When you add an [**Update App State**](../resources/data-representation/app-state.md#update-app-state-action) action via the Action Flow Editor, the corresponding pages will include this line within the build method:
 
 ```js
- @override
+@override
 Widget build(BuildContext context) {
     context.watch<FFAppState>();
     ...
@@ -155,4 +154,4 @@ These functions are automatically generated to provide a convenient and consiste
 
 :::info[How to create App State variables]
 To learn more about creating and using App State variables in FlutterFlow's UI, check out the[ **App State**](../resources/data-representation/app-state.md) guide.
-:::
+:::

docs/intro/before-you-begin/app-architecture.md

@@ -22,7 +22,7 @@ This includes:
 
 Backend usually refers to more complex logic and data storage. This includes:
 
-- Setting up a database that is capabale of storing, sending and retrieving data
+- Setting up a database that is capable of storing, sending and retrieving data
 - Leveraging off-the-shelf services, like authentication providers or payment platforms
 - Defining business logic, either by writing code or using a low-code tool
 

docs/intro/ff-ui/dashboard.md

@@ -74,7 +74,7 @@ You can also find links to various resources to assist in building apps with Flu
 - Additionally, ensure that you have added a name to your FlutterFlow profile. The same name will be used for the community forum profile.
 :::
 
-- **URL Access (Only Available for Enterprise Users)**: You can view and copy URLs that need to be whitelisted for FlutterFlow to function correctly in enterprise environments with restricted internet access. Check out docs on **[Whitelisting URLS](../../misc/enterprise-page.md#whitelist-urls)**.
+- **URL Access (Only Available for Enterprise Users)**: You can view and copy URLs that need to be whitelisted for FlutterFlow to function correctly in enterprise environments with restricted internet access. Check out docs on **[Whitelisting URLs](../../misc/enterprise-page.md#whitelist-urls)**.
 
     ![url-access](imgs/url-access-dashboard.avif)
 

docs/intro/ff-ui/storyboard.md

@@ -56,6 +56,6 @@ Watch this video if you prefer watching a video tutorial.
 ## FAQs
 
 <details>
-<summary>I am getting "Error: Unable to initialize Storyboard</summary>
+<summary>I am getting "Error: Unable to initialize Storyboard"</summary>
 <p>This error typically occurs because the initial page has not been set. To resolve this, please set the initial page in the [App Details](../../resources/projects/settings/general-settings.md#app-details) settings of your project.</p>
 </details>