Merge pull request #113 from FlutterFlow/fix-upload-type-correction

[Fixes]

Author: pinkeshmars

docs/ff-concepts/file-handling/upload-save-file.md

@@ -75,7 +75,7 @@ Go to your project page on FlutterFlow and follow the steps below to define the
 2. Select **Actions** from the Properties panel (the right menu), and click **Open**. This will open an **Action Flow Editor** in a new popup window.
 3. Click on the **+ Add Action**.
 4. Search and select the **Upload/Save File** (under *Utilities > Upload Data*) action.
-5. Set the [**Upload Type**](upload-data.md#types-of-upload). If you haven't integrated Firebase or Supabase yet, the default upload type will be *Local (Widget State)*.
+5. If you haven't integrated Firebase or Supabase yet, the default upload type will be **[Store media for upload](upload-data.md#local-upload-widget-state)**. However, once integrated, you can choose the **Upload Type** as [Firebase](upload-data.md#firebase), [Supabase](upload-data.md#supabase) or [Local (Widget State)](upload-data.md#local-upload-widget-state).
 6. Use the **File Type** dropdown to specify whether you want to upload a **PDF**, **Audio (MP3),** **ANY,** or **Uploaded Media**. The *Uploaded Media* option is there for uploading the media stored on the device. If you choose **Uploaded Media**, ensure you add one more same action (before this action) with **Upload Type** set to [**Local Upload (Widget State)**](upload-data.md#local-upload-widget-state).
 7. You can **Allow multiple Files** to be uploaded. After the multiple files are uploaded, you can access them via *Set from Variable menu > Widget State > Uploaded File URLs (`List <String>`).*
 8. To let users know whether the file is still being uploaded, you can enable the 'Show Snackbar' option.

docs/ff-concepts/file-handling/upload-save-media.md

@@ -76,7 +76,7 @@ Follow the steps below to add this action to any widget.
 1. Select the **Widget** (e.g., Button) on which you want to add the action.
 2. Select **Actions** from the **Properties Panel** (the right menu), and click **Open**. This will open an **Action Flow Editor** in a new popup window. If it's the first action, click **+ Add Action** button. Otherwise, click the "**+**" button below the previous action tile and select **Add Action**.
 3. Search and select the **Upload/Save Media** (under *Utilities > Upload Data*) action.
-4. Set the **Upload Type**. If you haven't integrated Firebase or Supabase yet, the default upload type will be *Local (Widget State)*.
+4. If you haven't integrated Firebase or Supabase yet, the default upload type will be **[Store media for upload](upload-data.md#local-upload-widget-state)**. However, once integrated, you can choose the **Upload Type** as [Firebase](upload-data.md#firebase), [Supabase](upload-data.md#supabase) or [Local (Widget State)](upload-data.md#local-upload-widget-state).
 5. Use the **Media Type/Source** to specify whether you want to upload a photo or a video, or both using this action.
 6. Using **Media Source** dropdown, you can choose between ***Camera***, ***Gallery**,* and ***Either Camera or Gallery*** (this option will bring up a bottom sheet from where the user can choose the media source as Camera or Gallery) and **Uploaded Media**. If you choose **Uploaded Media**, ensure you add one more same action (before this action) with **Upload Type** set to **Local Upload (Widget State)**.
 7. If you are uploading a photo, you can set a maximum width and height for it by using the **Max Width** and **Max Height** properties, respectively. This will modify the image dimension by maintaining the photo's aspect ratio.

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

@@ -9,6 +9,10 @@ keywords: [FlutterFlow, Deep Linking, Dynamic Linking, Concepts]
 
 # Deep & Dynamic Linking
 
+:::danger[Support for Dynamic Links]
+On August 25th, 2025, Firebase Dynamic Links will be shut down. It's recommended to start exploring alternative solutions for link management and deep linking. Read more about the [**announcement here**](https://firebase.google.com/support/dynamic-links-faq).
+:::
+
 Adding deep and dynamic linking allows you to share a special type of link that takes the user right
 inside the specific page of your app. You can also send the custom data with a link to load the page
 content based on the data.

docs/ff-integrations/maps/google-maps/google-maps-widget.md

@@ -204,6 +204,10 @@ Traffic on Map toggle.
 <div class="video-container"><iframe src="https://www.loom.
 com/embed/8cf915f27803412cb9b2247b5cfb257a?sid=45dac67a-0f2d-4f7d-a390-25b2ce8bc16f" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" referrerpolicy="strict-origin-when-cross-origin" allowfullscreen></iframe></div>
 
-
-
-
+## FAQ
+<details>
+<summary>Why Google Maps custom markers are not working in run mode or test mode?</summary>
+<p>
+Due to a recent update, Google Maps custom markers won't work in Run or Test mode unless CanvasKit is enabled. This is expected behavior. To use custom markers effectively, enable CanvasKit from [**Advanced Web Settings**](../../../resources/projects/settings/project-setup.md#advanced-web-settings).
+</p>
+</details>

docs/resources/control-flow/backend-logic/api/create-test-api-calls.md

@@ -119,6 +119,10 @@ Furthermore, the ability to import Swagger/OpenAPI definitions directly into Flu
 We also add all settings that are required to run the API, such as [headers](rest-api.md#headers), [query parameters](rest-api.md#query-parameters), [variables](rest-api.md#variables), and body as they are defined in the Swagger file. However, you might need to replace the hard-coded values in [Body](rest-api.md#body) text with the [variables](rest-api.md#variables).
 :::
 
+:::warning
+Please note that while it is possible to import APIs created with OAS 2.0 in FlutterFlow, you might face some issues, such as the body request being lost during the import process. Our import functionality is built based on the OAS 3.0 standard, so for the best experience and compatibility, it is recommended to use APIs that adhere to OAS 3.0 or above.
+:::
+
 To import API call definitions:
 
 1. Click the **Import OpenAPI** icon. This will open a new popup.

docs/resources/ui/components/built-in-components/chart/bar-chart.md

@@ -164,7 +164,7 @@ To customize the bar for each chart data:
 
 1. Select the **Chart** widget from the widget tree or the canvas area.
 2. Move to the properties panel, and open the **Chart Data** > **Bar Properties**.
-3. To change the **Bar Color**, click on the box next to the already selected color, select any dark/light color, and then click **Use Color** or click on an already selected color ****and enter a Hex Code directly.
+3. To change the **Bar Color**, click on the box next to the already selected color, select any dark/light color, and then click **Use Color** or click on an already selected color and enter a Hex Code directly.
 4. To add a border around the bar, enter the **Border Width** value and change its **Border Color**.
 
 

docs/resources/ui/components/built-in-components/chart/line-chart.md

@@ -156,7 +156,7 @@ To customize the line:
 
 1. Select the **Chart** widget from the widget tree or the canvas area.
 2. Move to the properties panel, open the **Chart Data** section and then open the **Line Properties** section.
-3. To change the **Line Color**, click on the box next to the already selected color, select any dark/light color, and then click **Use Color** or click on an already selected color ****and enter a Hex Code directly.
+3. To change the **Line Color**, click on the box next to the already selected color, select any dark/light color, and then click **Use Color** or click on an already selected color and enter a Hex Code directly.
 4. To change the thickness of the line, change the value in the **Line Thickness** input box.
 5. By default, all the data points are connected with a smooth curve line; to disable this, simply **turn off** the **Curved Lines** property. This will draw a straight line between two points.
     1. If you keep this property enabled, you may notice that for some data points the curve goes beyond/above the actual value. To prevent this, you can **enable** the **Prevent curve from overshooting**.