Merge branch 'main' into fix/json-predefined-path

Author: PoojaB26

docs/accounts-billing/payments-billing.md

@@ -5,7 +5,7 @@ This section contains information on the payment methods we accept and how to ch
 
 ## Invoices
 #### Can I Add A Tax ID (e.g. VAT) to my invoice?
-Unfortunately, at this time we are not able to process Tax IDs.
+If you need to include VAT in your invoices, please reach out to our support team at [email protected], and we’ll be happy to assist you with the process.
 
 
 ## Payment Methods

docs/ff-concepts/adding-customization/vscode-extension.md

@@ -231,6 +231,72 @@ To delete a Custom Action or Widget, delete the associated file.
 ### Adding New Dependencies
 You can add custom [pub.dev](https://pub.dev/) package dependencies with the `Dart: Add Dependency` command from the Visual Studio Code command palette. This will update the `pubspec.yaml` file.
 
+## Using Flutter Version Management (FVM)
+If you want to manage Flutter versions with [**Flutter Version Management (FVM)**](https://fvm.app/), you need to install it and add it to your system’s PATH. Follow these steps to get started:
+
+### Install FVM
+
+To install **FVM**, run the following command in your terminal. This installs FVM globally using Dart’s package manager.
+
+```
+dart pub global activate fvm
+```
+
+### Add FVM to Your System’s PATH
+
+After installation, you need to add the directory containing FVM’s executables to your **PATH variable** so that it can be accessed globally.
+
+#### For macOS & Linux
+
+1. Open the Terminal and run the following command. It adds the `~/.pub-cache/bin` directory to your system's `PATH` permanently by updating your `~/.zshrc` file. This ensures that the FVM installed in `~/.pub-cache/bin` is accessible from anywhere in the terminal.
+    
+    ```bash
+    echo 'export PATH="$PATH":"$HOME/.pub-cache/bin"' >> ~/.zshrc  # For Zsh
+    echo 'export PATH="$PATH":"$HOME/.pub-cache/bin"' >> ~/.bashrc # For Bash
+    ```
+    
+2. Restart your terminal or run `source ~/.zshrc` (or `source ~/.bashrc`) to apply the changes.
+
+#### For Windows
+
+1. Locate the **FVM executable path**, typically:
+    
+    ```
+    C:\Users\YourUsername\AppData\Local\Pub\Cache\bin
+    ```
+    
+2. Add this path to your **System’s PATH variable**:
+    1. Open **System Properties** → **Advanced system settings**.
+    2. Click **Environment Variables**.
+    3. Under **System variables**, select **Path** → **Edit**.
+    4. Click **New** and add the above path.
+    5. Click **OK** and restart your terminal.
+
+
+### Verify the Installation
+
+To check if FVM is correctly installed and accessible, run:
+
+```bash
+fvm --version
+```
+
+If this command prints the installed version of FVM, it means FVM is successfully installed and added to PATH.
+
+
+### Configure FVM in Your Flutter Project
+
+Once FVM is installed, navigate to your Flutter project folder and set up FVM:
+
+```bash
+cd your-flutterflow-project
+fvm init
+fvm install <flutter_version>
+fvm use <flutter_version>
+```
+
+*(Replace `<flutter_version>` with the required Flutter version.)*
+
 
 ## FAQs
 <details>

docs/ff-concepts/navigation-routing/imgs/share-action.avif

@@ -9,54 +9,10 @@ keywords: [FlutterFlow, Share Action, Navigation, Concepts]
 
 # Share [Action]
 
-Share Action can be used to send a text using the Android or iOS device's share dialog. You can send the text using email, message, or any other application present on the device that supports sharing functionality.
-
-<figure>
-    <img src="https://firebasestorage.googleapis.com/v0/b/ecommerceflow-docs/o/share-example.gif?alt=media&token=f902c889-56e0-4f40-9413-7e5852d5d8c2"></img>
-  <figcaption class="centered-caption"></figcaption>
-</figure>
-
-## Define Share Action
-
-Go to your project page on FlutterFlow and follow the steps below to define an Upload Photo/Video Action to a widget:
-
-1. Select the **widget** in which you want to set the Action.
-
-2. Select the **Actions** from the Properties Panel (the right menu).
-
-3. Click **+ Add Action** button.
-
-4. Choose a gesture from the dropdown among ***On Tap****,* ***On Double Tap****,**or* **On Long 
-   Press**.
-
-5. Select the **Action Type** as ***Share***.
-
-6. Now, you need to specify a **URL/Text Value**. It can be set either by defining a **Specific 
-   Value** or by using **From Variable** to use a value stored inside a variable. 
-   - If you are using **Specific Value**, enter the text in the **Value** field. 
-   - If you are using **From Variable**, you need to select the **Source**.
-
-Demo of defining Share Action using a **Specific Value** is as follows:
-
-<img src="https://firebasestorage.googleapis.com/v0/b/ecommerceflow-docs/o/share-with-value.gif?alt=media&token=415cf039-dae7-4ee0-ad3c-c31a8c5c4a50"></img>
-
-<p></p>
-
-Alternatively, a demo of defining Share Action using **From Variable** option is as follows:
-
-<p></p>
-
-
-<figure>
-    <img src="https://firebasestorage.googleapis.com/v0/b/ecommerceflow-docs/o/share-with-variable.gif?alt=media&token=7d77df34-7c82-47fe-ba50-8eedf699c6ea"></img>
-  <figcaption class="centered-caption"></figcaption>
-</figure>
-
+The **Share Action** enables users to send text or URLs from your app using the native sharing capabilities of their device. This functionality allows users to share information through various applications installed on their devices, such as email, messaging apps, or social media platforms.
 
 :::warning
-You won't be able to try out this Action using FlutterFlow's *Run Mode* or *Preview Mode*. To 
-test this Action, you have to run it on an iOS or Android device or emulator. You can either 
-**Download the Code** (by going to `Developer Menu > Download Code`) and build it for your 
-device, or use the **Build APK** button (present on the [**Tool Bar**](../../intro/ff-ui/toolbar.md) to generate an APK that 
-you can run on your Android device.
+It's important to note that the Share Action is designed for mobile platforms and is not supported in FlutterFlow's Run Mode or Preview Mode. To test this functionality, you need to [**run your app on an iOS or Android device or emulator**](../../testing-deployment-publishing/running-your-app/local-run.md).
 :::
+
+![share-action](imgs/share-action.avif)

docs/ff-concepts/navigation-routing/share-action.md

@@ -168,9 +168,9 @@ com/embed/1abddd1120db477da2c085dbc6b7a742?sid=5b161c8b-3957-4ac9-b27f-dc5ebc03f
 
 
 
-## Enable Billing for Cloud Functions Access
+## Enable Billing
 
-If you want to deploy functions (e.g., Braintree payments, Push Notifications), you will need to enable billing for your Firebase project. Please follow these steps to enable billing:
+If you want to deploy [Cloud Functions](https://firebase.google.com/products/functions) (e.g., Braintree payments, Push Notifications) or use [Firebase Cloud Storage](https://firebase.google.com/products/storage), you will need to enable billing for your Firebase project. Please follow these steps to enable billing:
 
 1. From the Firebase dashboard of your project, navigate to the far left menu. Under Build, select **Functions** and then select **Upgrade project**.
 

docs/ff-integrations/firebase/connect-to-firebase-setup.md

@@ -203,10 +203,30 @@ A seamless and positive test experience is crucial for users to evaluate your Fl
 
 #### 4.1 Functional Run Mode Link
 
-- **Criteria:** The provided Run Mode link must be active and correctly load a working demo of your project.
-- **Why it Matters:** The Run Mode link is the primary way users can interact with your project before purchasing. A broken or inaccessible link creates a significant barrier.
-- **What To Do:**
-    - **Double-check your link:** Before submitting, test the link multiple times to confirm it showcases the experience you want potential buyers to have.
+- **Criteria:** The provided Run Mode link must be active and correctly load a working demo of your project. For mobile-only features or utility libraries that cannot be demonstrated in Run Mode's web environment, you must provide alternative demonstration methods.
+- **Why it Matters:** The Run Mode link is the primary way users can interact with your project before purchasing. A broken, inaccessible, or non-demonstrative link creates a significant barrier to understanding the item's value.
+- **What To Do:**
+    - **For Standard Web-Compatible Items:**
+        - Double-check your link before submitting to confirm it showcases the experience you want potential buyers to have.
+        - Test the link multiple times to ensure consistent functionality.
+    - **For Mobile-Only Features:**
+        - Create a dedicated demonstration page in your project that explains the mobile-only functionality.
+        - Include screenshots, videos, or mockups showing how the feature works on mobile devices.
+        - Clearly indicate which features are mobile-only and why they cannot be demonstrated in Run Mode.
+        - Optionally, provide a published FlutterFlow web deploy link that can be used instead of the Run Mode URL.
+    - **For Utility Libraries (e.g., Analytics, Background Services):**
+        - Create a demonstration page that explains the library's functionality.
+        - Show configuration options and expected outcomes.
+        - Include visual aids like flowcharts or diagrams to explain the library's operation.
+        - Provide example code or configuration snippets.
+        - Consider adding debug/test outputs that demonstrate the library is working.
+    - **Documentation:**
+        - Regardless of the type of item, ensure your documentation clearly explains how to implement and test the functionality in a real mobile environment.
+        - Include troubleshooting guides and common implementation scenarios.
+
+:::tip
+For items that cannot be fully demonstrated in Run Mode, focus on creating a clear, informative demonstration page that helps users understand the value and implementation of your item. Visual aids, clear explanations, and comprehensive documentation are key to helping users make informed decisions.
+:::
 
 #### 4.2 User Sign-In (Anonymous Auth)
 
@@ -251,7 +271,7 @@ Building a solid app template goes beyond surface-level design. It's about creat
 #### 5.2 No Pixel Overflow
 
 - **Criteria:** Ensure your UI elements are positioned and sized correctly to avoid content overflowing its container, leading to visual glitches / cut off content.
-- **Why It Matters:** Pixel overflows are a sign of UI inconsistencies that can negatively impact the user experience, especially on different screen sizes. Pixel overflow issues can occur in Test Mode when there’s a hardcoded pixel value and not enough space on the screen to render that exact value.
+- **Why It Matters:** Pixel overflows are a sign of UI inconsistencies that can negatively impact the user experience, especially on different screen sizes. Pixel overflow issues can occur in Test Mode when there's a hardcoded pixel value and not enough space on the screen to render that exact value.
 - **What To Do:**
     - **Preview pixel overflows:** Toggle the pixel overflow icon in the top-right of the canvas to see if there are any overflow issues.
     - **Leverage FlutterFlow's layout tools:** Use Expanded and Flex values to help prevent layout issues. Make `Columns` or `Rows` scrollable to prevent overflows. Use auto-sizing text or text clipping where it makes sense. Remove hard-coded width and height where it makes sense.

docs/marketplace/creators-hub/submission-criteria.md

@@ -33,7 +33,7 @@ A list of all the available global properties is as follows:
 
 - **Current Device Location:** Obtains he user's current location, ideal for updating their position on Google Maps or storing it in a backend database. [Check out examples](#current-device-location) on how to retrieve and save the current device location.
 
-- **Link To Current Page:** Provides the deep link of the current page. Learn more about [adding deep links here](../../ff-concepts/navigation-routing/deep-dynamic-linking.md#adding-deep-link).
+- **Current Route Path**: Provides the route name of the currently active or visible page in your app. This property is especially helpful in scenarios where you want to adjust or block specific actions if the active page isn't the one you expect. For example, if you launch the app through a push notification, the home page might still run in the background, even if the notification directs you to a different page. Using this property, you can prevent unnecessary action triggers, such as On Page Load from the home page. See details on avoiding [this issue](https://github.com/FlutterFlow/flutterflow-issues/issues/2765#issuecomment-2598915946).
 - **Fraction of Screen Width:** Determines the proportional width of the device's screen.
 - **Fraction of Screen Height:** Determines the proportional height of the device's screen.
 - **Screen Width:** Provides the total width of the current device's screen in pixels.
@@ -45,7 +45,7 @@ A list of all the available global properties is as follows:
 - **Is Dark Mode:** Checks if the app's current theme mode is set to dark.
 - **Is Light Mode:** Checks if the app's current theme mode is set to light.
 - **Is On-Screen Keyboard Visible:** Checks if the on-screen or soft keyboard is visible. This is helpful in making UI adjustments if keyboard is visible on screen. See a [quick example](#is-on-screen-keyboard-visible). 
-
+- **Current Environment**: Gives you the current [development environment](../../testing-deployment-publishing/development-environments/development-environments.md) value.
 
 :::tip[Generated Code]
 Learn more about the [**Generated Code**](../../ff-concepts/state-management/generated-code.md#global-state) behind Global Properties.

docs/resources/data-representation/global-properties.md

@@ -80,6 +80,17 @@ To publish a FlutterFlow project as a library, start by creating a FlutterFlow p
 - It's recommended to include a message that tells users what has changed in the version your are publishing.
 :::
 
+:::warning
+To publish a project as a library, it must meet the following requirements:
+
+- **No Prior Store Deployment**: The project must not have been deployed to the Google Play Store or Apple App Store.
+- **No Failed Deployments**: The Publish button remains disabled if a deployment process was started and failed.
+- **No Errors or Warnings**: All project errors or warnings must be addressed beforehand.
+- **Main Branch Only**: You can only publish from the main branch.
+- **Pro Plan Subscription**: A Pro Plan is required to publish a project as a Library.
+- **Not Cloned from Marketplace**: The project cannot be a clone of a Marketplace item.
+:::
+
 ### Disabled Features in a Library
 
 When a project is converted into a library, the following features are disabled to ensure compatibility and functionality limitations:
@@ -136,7 +147,7 @@ To import a library project into another FlutterFlow project, you must go to the
 - By default, the latest published version of the library is imported, but you can choose to depend on an earlier version if needed.
 - You can also import the `current` version of the library to use the latest state of the library on the main branch - however, this is not recommended.
 - You must have a paid plan to import a library.
-
+- When importing a library into a project or another library, the library’s version must not be set to 'current' and should be less than or equal to the FlutterFlow version of the project or library it’s being imported into. Learn more about [**managing Library’s FlutterFlow version**](../projects/settings/version-management.md#version-management-with-libraries).
 :::
 
 
@@ -232,6 +243,8 @@ You can easily upgrade to newer versions of the libraries as they become availab
 
 ![update-library](imgs/update-library.avif)
 
+
+
 ## Library Values
 
 **Library values** are essentially variables created and used by a library author and intended to have their values set by the library user. These values allow library author to create configurable variables that are useful in different contexts, such as API keys, global settings, or other project-specific configurations. These values allow library users to input specific data required for the library to function properly in their project.