Merge branch 'main' into feature/code-expression

Author: PoojaB26

docs/accounts-billing/plan-pricing.md

@@ -299,6 +299,9 @@ I am a Free user and have more than 2 projects – what will happen to them?
       <li>
         **Marketplace exception:** Existing Free plan projects published to the Marketplace prior to August 18, 2025 will not count toward your 2-project limit. If a project is later removed from Marketplace and you exceed the limit, it will be automatically archived.
       </li>
+      <li>
+        Archived projects are never deleted. If you later upgrade to a paid plan, you'll regain full access to edit and publish them.
+      </li>
     </ul>
   </li>
   <li>

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

@@ -68,7 +68,9 @@ necessary code.
 This can significantly speed up the building process and reduce the need for in-depth programming
 knowledge, making it especially useful for custom functions and actions.
 
-**Limitation:** The prompts are limited to 100 characters currently.
+:::info[Limitation]
+Your prompt must be at least 3 words and no more than 500 characters.
+:::
 
 <div style={{
     position: 'relative',

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

@@ -27,7 +27,7 @@ You can add and send push notifications manually or trigger them based on user a
 :::info[General Prerequisites]
 Before you begin, ensure that you:
 - Complete all the steps in 
-[**Firebase Setup**](../../ff-integrations/firebase/connect-to-firebase-setup.md).
+[**Firebase Setup**](../../ff-integrations/firebase/connect-to-firebase-setup.md). Note that, while setting up, make sure to follow step number 5 and 8 carefully from [**Allow FlutterFlow to Access Your Project**](../../ff-integrations/firebase/connect-to-firebase-setup.md#allow-flutterflow-to-access-your-project) section to properly add the **Cloud Functions Admin** role to **[email protected]** user.
 - Upgrade your Firebase project to the [**Blaze plan**](https://firebase.google.com/pricing) to enable [**Cloud Functions**](https://firebase.google.com/docs/functions), which are required specifically for FlutterFlow’s push notification setup, such as retrieving the FCM token and sending notifications trigger from FlutterFlow.  
 :::
 

docs/ff-concepts/notifications/push-notifications.md

@@ -21,7 +21,7 @@ Here are some examples of AI Agents:
 
 :::info[Prerequisite]
 Before you begin setting up AI Agents, make sure you:
-1. Connect your project to Firebase by completing the [**Firebase Setup**](../firebase/connect-to-firebase-setup.md).
+1. Complete all the steps in [**Firebase Setup**](../firebase/connect-to-firebase-setup.md). Note that, while setting up, make sure to follow step number 5 and 8 carefully from [**Allow FlutterFlow to Access Your Project**](../firebase/connect-to-firebase-setup.md#allow-flutterflow-to-access-your-project) section to properly add the **Cloud Functions Admin** role to **[email protected]** user.
 2. Upgrade your Firebase project to the [**Blaze Plan**](https://firebase.google.com/pricing), as we rely on [**Firebase Cloud Functions**](https://firebase.google.com/docs/functions) to handle AI-related communication securely.
 :::
 

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

@@ -58,7 +58,7 @@ Integrating the Stripe Payments in your app comprises the following steps:
 4. [Testing](#4-testing)
 5. [Releasing to production](#5-releasing-to-production)
 
-### 1. Setup Stripe payment
+### 1. Setup Stripe Payment
 
 Setting up the Stripe payment includes acquiring the keys from your Stripe account and adding them to FlutterFlow.
 
@@ -76,7 +76,7 @@ Follow the steps below to set up payment using Stripe:
 6. Copy the **Publishable Key** and **Secret Key** from the Stripe API keys page and paste them into the respective fields inside FlutterFlow. If you are using Stripe in test mode, make sure you paste them inside the **Test Credentials** section.
 7. Under the **Additional Settings**, you need to specify the following:
     1. **Merchant Display Name** (*Required*): Enter a name for the merchant (you) that the user will see while performing the payment.
-    2. **Merchant Country Code** (*Required*): Enter your country code. This must be the 3-digit ISO country code, such as USA, IND, and NGA.
+    2. **Merchant Country Code** (*Required*): Enter your country code. This must be the 2 digit ISO country code, such as US, IN, and AU.
     3. **Apple Merchant ID** (*Optional*): You need to enter this if you want to accept payments through Apple Pay as well. The instructions for using Apple Pay are in [this section](#2-apple-pay-setup-optional).
 8. Click **Deploy**.
 
@@ -86,7 +86,7 @@ Follow the steps below to set up payment using Stripe:
     height: 0,
     width: '100%'}}>
     <iframe 
-        src="https://www.loom.com/embed/0e4ba1f7f055433e96a7fa6cede2c127?sid=400ef912-1580-44ad-81a9-25051bed0256"
+        src="https://demo.arcade.software/PcikYUtB8cSug9CyUAOv?embed&show_copy_link=true"
         title=""
         style={{
             position: 'absolute',
@@ -108,7 +108,7 @@ Follow the steps below to set up payment using Stripe:
 
 This would deploy the Stripe payment service as a Firebase Cloud Function. Now, you are ready to trigger payments inside your app.
 
-### 2. Apple Pay setup (optional)
+### 2. Apple Pay Setup (optional)
 
 Setting up Apple Pay comprises the following steps:
 
@@ -185,7 +185,7 @@ To add Apple Merchant ID in FlutterFlow:
 
 ![Adding Apple Merchant ID in FlutterFlow](imgs/adding-apple-merchant-id.png)
 
-### 3. Trigger Stripe payment [Action]
+### 3. Trigger Stripe Payment [Action]
 
 In order to initiate a payment using Stripe, you have to use the **Stripe Payment** action.
 
@@ -244,7 +244,7 @@ You can test Stripe payments on mobile and the Web before deployment. To do that
 4. [Download](../../testing-deployment-publishing/exporting-code/ff-cli.md) and [run](../../testing-deployment-publishing/running-your-app/run-your-app.md) your project..
 5. To test the purchase, you can use any of these [basic test card numbers](https://stripe.com/docs/testing#cards).
 
-### 5. Releasing to production
+### 5. Releasing to Production
 
 Before you release the app to production, complete the following steps:
 

docs/ff-integrations/payments/stripe.md

@@ -114,3 +114,17 @@ Here's a quick guide to updating the app state variable. We need to add an actio
     </iframe>
 </div>
 
+## FAQs
+
+<details>
+<summary>
+Why are some variable types not available in App State?
+</summary>
+<p>
+Certain variable types, e.g., **Firestore Documents** and **Supabase Row**, can be used in Page State or Component State, but not in App State. This is because App State variables are designed to be global, meaning they stay in memory throughout the app. When App State variables are marked as persisted, the variable’s value is saved to the device’s local storage.
+
+Storing large or complex data types like documents in App State could lead to **performance or size issues**, especially on lower-end devices. For this reason, FlutterFlow limits App State to lightweight types, while Page/Component State allows for more flexibility since their scope is smaller and temporary.
+
+If you need to work with such data types, it's recommended to store them in Page or Component state instead.
+</p>
+</details>

docs/resources/data-representation/app-state.md

@@ -68,7 +68,42 @@ When naming custom data types, always use **UpperCamelCase**, as recommended by
 
 ## Accessing Custom Data Type
 
-After creating the custom data type, you can use it to create variables, such as an app state variable, and then access them. Here's an [example](app-state.md#app-state-variables).
+After creating a custom data type, it’s treated internally as a [Dart class](https://dart.dev/language/classes). However, just defining the custom data type doesn’t hold any real data. To work with actual data, such as storing a user profile or a review, you need to create an **instance** of custom data type.
+
+Creating an instance allows you to:
+
+- Assign specific values to each field in your custom data type.
+- Store the instance in app state, page state, or pass it between widgets.
+- Access individual fields wherever needed.
+
+To create an instance of a custom data type, first you need to [create a state variable](../../ff-concepts/state-management/state-variables.md#creating-state-variables) (of type **Data Type**) that will hold the instance. Then, to create and add the instance to the state variable, open the **Set from Variable** dialog and select **Create Data Type Object > Project Data Type**. Choose the data type you want to use. After that, set values for each of the required fields.
+
+
+<div style={{
+    position: 'relative',
+    paddingBottom: 'calc(56.67989417989418% + 41px)', // Keeps the aspect ratio and additional padding
+    height: 0,
+    width: '100%'}}>
+    <iframe 
+        src="https://demo.arcade.software/qNNwqEm7vrvuWszmhf9R?embed&show_copy_link=true"
+        title=""
+        style={{
+            position: 'absolute',
+            top: 0,
+            left: 0,
+            width: '100%',
+            height: '100%',
+            colorScheme: 'light'
+        }}
+        frameborder="0"
+        loading="lazy"
+        webkitAllowFullScreen
+        mozAllowFullScreen
+        allowFullScreen
+        allow="clipboard-write">
+    </iframe>
+</div>
+<p></p>
 
 ### Custom Data Type in Custom Code
 Sometimes, you might want to access the custom data type in your custom code. Our custom code editor allows you to receive and pass data into a variable of a custom data type. For example, you could manipulate or analyze the data as needed, and then return the modified result in the custom data type. 

docs/resources/data-representation/custom-data-types.md

@@ -430,3 +430,14 @@ We're working on Library Values, which will allow users to set specific values w
 Projects can import libraries that themselves have imported other Libraries as dependencies. However, if the project and the library share the same dependency, the version must match exactly to avoid conflicts.
 </p>
 </details>
+
+<details>
+<summary>Why do I get collision errors when importing a duplicated project as a library?</summary>
+<p>
+When you duplicate a project and publish it as a library, the unique identifiers (keys) for components and other resources are not automatically changed. If you then import this library back into the original project, it causes key collisions between the original and duplicated resources.
+
+To help with this, FlutterFlow shows a dialog that offers to automatically delete the original resources in your base project and update all references to point to the library versions.
+
+If you prefer to resolve this manually, you can duplicate individual components within the library after importing, this will generate new keys and avoid the collision.
+</p>
+</details>