updated content, consolidated and reorganized the articles

Author: mrdavidorok

docs/ff-concepts/adding-customization/add_dependencies_to_custom_widgets_or_actions_in.md

@@ -1,43 +1,37 @@
 ---
-keywords: ['permissions', 'upload', 'view']
-slug: enable-image-upload-in-webview-on-device
+keywords: ['permissions', 'upload', 'webview', 'image']
+slug: enable-image-upload-in-webview-on-real-devices
 title: Enable Image Upload in WebView on Real Devices
 ---
 
-# Enable Image Upload in WebView on Real Devices
+## Enable Image Upload in WebView on Real Devices
 
-Image uploads may work in Run/Test mode but fail on real devices due to missing runtime permissions related to accessing the photo library.
+Image uploads may function correctly in Run/Test mode but fail on real devices due to missing runtime permissions required for accessing the photo library. This document outlines the steps to resolve this issue.
 
-## Problem
+In web preview mode, the browser handles permissions, allowing image uploads to proceed without specific configurations. However, when deploying to physical Android or iOS devices, explicit runtime permissions are necessary to access the device's photo library. If image upload functionality is embedded within a **WebView**, FlutterFlow does not automatically detect this requirement and therefore does not request the required permissions during the build process.
 
-In web preview mode, permissions are managed by the browser, and image upload typically works without issues. However, on physical devices, accessing the photo library requires explicit runtime permissions.
+To enable image uploads from a **WebView** on a physical device, follow these steps:
 
-If the image upload is implemented inside a WebView, FlutterFlow does not automatically detect it and therefore does not request the necessary permissions.
+1.  **Enable Photo Library Permission:**
 
-## Solution
+      Navigate to **Settings > [Permissions](/settings-and-integrations/mobile-deployment/permissions)** in your FlutterFlow project and enable the **Photo Library** permission.
 
-To allow image uploads from a WebView on a physical device, follow these steps:
+         ![](../assets/20250430121337121891.png)
 
-1. **Enable the Required Permission**  
-   Navigate to **Settings → Permissions** in your FlutterFlow project and enable the **Photo Library** permission.
+2.  **Request Permission at Runtime:** 
+      Before initiating the image upload action inside the **WebView**, add a **[Get Permission](/actions/widget-actions/permissions/get-permission)** action. Configure this action to explicitly request access to the **Photo Library**. This action should typically be placed on a button tap or an equivalent user interaction that precedes the upload.
 
-   ![](../assets/20250430121337121891.png)
+         ![](../assets/20250430121337385659.png)
 
-2. **Request Permission at Runtime**  
-   Before initiating the upload action inside the WebView, use the **Get Permission** action to explicitly request access to the photo library.
+3.  **Reinstall the Application:** 
 
-   ![](../assets/20250430121337385659.png)
+      After adding and configuring the permission, it is crucial to re-deploy your application to the device:
+         * Uninstall any existing versions of the app from the target device.
+         * Clear the app's cache (if applicable).
+         * Reinstall the updated application. This step ensures that the permission prompt appears when the app is launched for the first time or when the `Get Permission` action is triggered.
 
-3. **Reinstall the App**  
-   After adding the permission:
-   - Uninstall the app from the device.
-   - Clear the app cache.
-   - Reinstall the app to ensure the permission prompt appears.
+            :::warning
+            If the permission dialog does not appear on the first launch or when the `Get Permission` action is triggered, the app will not have access to the photo library, and uploads inside the **WebView** will fail. Users may need to manually enable the permission through their device's app settings.
+            :::
 
-## Notes
-
-:::warning
-If the permission dialog does not appear on first launch, the app will not have access to the photo library, and uploads inside the WebView will fail.
-:::
-
-Once permissions are correctly granted, image uploads inside the WebView will function as expected on physical devices.
+Once permissions are correctly granted, image uploads initiated from within the **WebView** will function as expected on physical devices.

docs/ff-concepts/adding-customization/enable_image_upload_in_webview_on_device.md

@@ -0,0 +1,30 @@
+---
+keywords: ['login', 'authentication', 'snackbar', 'error']
+slug: /display-error-message-for-invalid-login-credentials
+title: Display Error Message for Invalid Login Credentials
+---
+
+# Display Error Message for 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.
+
+**Customize the SnackBar (Optional)**
+
+    To add custom logic or change the appearance:
+
+    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.
+
+:::tip
+There is no need to manually add alert dialogs for failed login attempts. FlutterFlow handles `SnackBar` display automatically when authentication fails.
+:::
+
+:::note
+To customize the `SnackBar` further, use the **Action Output** and attach additional logic based on the error string.
+:::

docs/ff-concepts/alerts/Create an alert if a user's email address or password is invalid.md

@@ -0,0 +1,26 @@
+---
+keywords: ['list', 'missing', 'state']
+slug: /missing-data-types-in-app-state-variable-list
+title: Missing Data Types in App State Variable List
+---
+
+# Missing Data Types in App State Variable List
+
+When creating an **App State Variable** in FlutterFlow, you should see a list of available data types. However, in some cases—especially in older projects—these data types may not appear.
+
+This issue is typically caused by the **Deep Linking** setting being turned off in your project. If Deep Linking is disabled, the data type selection list may not populate correctly.
+
+Follow the steps below to enable Deep Linking and restore the missing data types:
+
+    1. Open your FlutterFlow project.
+    2. Go to **Settings > App Details**.
+    3. Scroll to the **Deep Linking & Route** section.
+    4. Enable the **Deep Linking** toggle.
+
+    ![](../assets/20250430121217509964.png)
+
+    After enabling Deep Linking, the list of data types should now be visible when adding or editing an App State Variable.
+
+    :::note
+    This fix is particularly effective for older projects where the setting may be disabled by default.
+    :::