updated content, improved formatting

Author: mrdavidorok

docs/troubleshooting/apple-store-deployment-issues/fetch signing-files/_category_.json

@@ -1,3 +1,3 @@
 {
-  "label": "Fetching Siging Files"
+  "label": "Fetching Signing Files"
 }

docs/troubleshooting/apple-store-deployment-issues/fetch signing-files/codemagic_install_pods_failure.md

@@ -6,58 +6,51 @@ title: Codemagic Install Pods Failure
 
 # Codemagic Install Pods Failure
 
-During Codemagic deployment, errors may occur at the **Install Pods** step due to issues related to iOS dependency management. This article outlines common causes and solutions to resolve these errors.
+During Codemagic deployment, errors may occur at the **Install Pods** step due to iOS dependency conflicts, unstable code branches, or pod version mismatches. This guide outlines steps to identify and resolve these issues effectively.
 
-## Custom Code Package Conflicts
+:::info[Prerequisites]
+- You are deploying an iOS app using Codemagic.
+- Your project includes custom code or third-party packages.
+:::
 
-Conflicts between custom code packages and existing project dependencies can prevent pods from installing correctly. Flutter dependencies have version constraints, and introducing new packages or updating versions without checking compatibility may cause version conflicts.
+## Fix Dependency Conflicts from Custom Code
 
-**Solution:**
+Custom code or third-party packages may introduce conflicting versions of dependencies that prevent CocoaPods from resolving successfully.
 
-  - Check package documentation for compatibility issues.
-  - Update package versions in `pubspec.yaml` to versions known to be compatible.
-  - Run `flutter pub get` to refresh dependencies.
+**Steps to Resolve Install Pods Failure:**
 
-    For example, the package `platform_device_id` may cause conflicts:
+- **Check for Dependency Conflicts from Custom Code**  
+   Custom or third-party packages may cause version mismatches with FlutterFlow-supported dependencies.
 
-    ![](../../assets/20250430121132533922.png)
+   - Review documentation to ensure package compatibility.
+   - Adjust versions in your `pubspec.yaml` file accordingly.
+   - Run:
 
-## Deployment from an Incompatible GitHub Branch
+     ```bash
+     flutter pub get
+     ```
 
-Deploying from a GitHub branch that contains untested custom code or recent dependency changes may result in deployment failures.
+      ![](../../assets/20250430121132533922.png)
 
-  **Solution:**
+- **Use a Stable GitHub Branch for Deployment**  
+   Deploying from unstable branches can introduce unexpected errors during pod installation.
 
-    - Use a stable, fully tested branch for deployment.
-    - Merge the latest stable changes into the deployment branch.
-    - Remove experimental or untested code that may affect deployment.
+   - Ensure you're using a branch that passed previous Codemagic deployments.
+   - Remove untested or experimental code.
+   - Revert or refactor recent commits that might break dependencies.
 
-      For example, the branch `dungtienle/folhavpnV3` may contain unstable code:
+   ![](../../assets/20250430121132883140.png)
 
-      ![](../../assets/20250430121132883140.png)
+- **Fix Pod Version Compatibility Issues**  
+   CocoaPods may fail to resolve dependencies due to incompatible versions or incorrect iOS deployment targets.
 
-    - Review recent commits to identify and address changes affecting pod installation.
-    - Revert problematic commits if necessary.
+   - Update packages like `app_settings` in `pubspec.yaml` to versions compatible with your Flutter version.
+   - Raise the iOS minimum deployment target in Xcode if necessary.
 
-## Incompatible Pod Versions
+   ![](../../assets/20250430121133219967.png)
 
-CocoaPods may fail to resolve compatible versions for specific pods, such as `app_settings`, especially if the pod version conflicts with other pods or the iOS deployment target.
-
-  **Solution:**
-
-    - Update the version of `app_settings` in `pubspec.yaml` to a compatible version.
-    - If necessary, increase the iOS minimum deployment target using Xcode.
-
-      For example, the engineering team identified `app_settings` as the cause:
-
-      ![](../../assets/20250430121133219967.png)
-
-    - Adjust the iOS deployment target following Apple's or Amplify’s iOS platform setup guidance.
-
-  :::info[Deployment Best Practices]
-  - Verify package compatibility before adding new dependencies or upgrading existing ones.
-  - Always deploy from stable, tested branches.
-  - Ensure the iOS deployment target version meets the requirements of all packages and pods.
-  :::
-
-  By following these steps, you can resolve the **Install Pods** error and successfully deploy your app with Codemagic in FlutterFlow.
+:::tip[Deployment Best Practices]
+- Confirm dependency compatibility before pushing changes.
+- Always deploy from tested GitHub branches.
+- Verify your deployment target supports all pods used.
+:::

docs/troubleshooting/apple-store-deployment-issues/fetch signing-files/codemagic_signing_certificate_limit.md

@@ -6,31 +6,41 @@ title: Codemagic Signing Certificate Limit
 
 # Codemagic Signing Certificate Limit
 
-During deployment, Codemagic attempts to create distribution certificates in your Apple Developer Account. If you have reached the maximum number of allowed distribution certificates, this process will fail, preventing a successful build.
+During iOS deployment, Codemagic attempts to create distribution certificates in your Apple Developer Account. If the maximum number of certificates has already been reached, the build will fail with a certificate creation error.
 
-**Full Error Message**
+## Error Message
 
-```
-Build failed :|Step 3 script `Fetch signing files` exited with status code 1Returned 409: There is a problem with the request entity - You already have a current Distribution certificate or a pending certificate request.
+```bash
+Build failed :|Step 3 script `Fetch signing files` exited with status code 1
+Returned 409: There is a problem with the request entity - You already have a current Distribution certificate or a pending certificate request.
 ```
 
-This error indicates that Codemagic cannot create a new certificate because existing certificates or pending certificate requests are already using the available slots.
+This message indicates that Codemagic cannot proceed because no additional distribution certificates can be created.
 
-**Solution**
+:::info[Prerequisites]
+- You are deploying an iOS app using Codemagic.
+- Your Apple Developer Program account is active and linked.
+:::
 
-To resolve this issue, delete unused distribution certificates from your Apple Developer account to free up space for new certificates.
+**Steps to Resolve Certificate Limit Error:**
 
-    **Steps to Delete Certificates**
+1. **Access Your Apple Developer Account**  
+   Log into your Apple Developer account to manage certificates:
 
-        - Open your **[Apple Developer Account](https://developer.apple.com/account/resources/certificates/list)**.
-        - Navigate to **Certificates, Identifiers & Profiles**.
-        - Under **Certificates**, review the list of existing certificates.
-        - Locate and delete any unused or expired **Distribution Certificates**.
+        - Go to the **[Apple Developer Certificates List](https://developer.apple.com/account/resources/certificates/list)**.
 
-    After removing unnecessary certificates, re-run the deployment from FlutterFlow.
-    
-    :::note
-    The deleted certificates will be recreated automatically by Codemagic during the next build process.
-    :::
+2. **Navigate to the Certificates Section**  
+   In the **Certificates, Identifiers & Profiles** section:
+
+        - Click on **Certificates**.
+        - Locate all existing **Distribution Certificates**.
 
-    
+3. **Remove Unused or Expired Certificates**  
+   Review and delete any unused, expired, or redundant distribution certificates to free up space.
+
+4. **Re-run Deployment**  
+   After deleting the certificates, initiate the build process again in FlutterFlow. Codemagic will automatically generate a new certificate as needed.
+
+    :::note
+    The deleted distribution certificates will be recreated automatically by Codemagic during the next build.
+    :::

docs/troubleshooting/apple-store-deployment-issues/fetch signing-files/ios_deployment_authentication_error.md

@@ -6,50 +6,54 @@ title: iOS Deployment Authentication Error
 
 # iOS Deployment Authentication Error
 
-During iOS deployment using Codemagic, you may encounter an authentication credentials error due to misconfigured or expired tokens while setting up App Store deployment.
+During iOS deployment using Codemagic, an authentication credentials error can occur due to misconfigured or expired API tokens for App Store deployment.
 
-**Invalid Authentication Credentials**
+The API token used for App Store Connect may be invalid or expired.
 
-This error indicates that the API token used for App Store Connect is either expired or invalid.
+:::info
+For details on generating valid tokens, see the **[Apple API Token Documentation](https://developer.apple.com/go/?id=api-generating-tokens)**.
+:::
 
-For detailed information on generating valid tokens, refer to the **[Apple API Token Documentation](https://developer.apple.com/go/?id=api-generating-tokens)**.
+Here is the error message:
 
-**Full Error Message**
-
-```
+```bash
 Failed Step: Fetch signing files
 GET https://api.appstoreconnect.apple.com/v1/bundleIds?limit=100&sort=name&filter%5Bidentifier%5D=appname.com&filter%5Bplatform%5D=IOS returned 401: Authentication credentials are missing or invalid. Provide a properly configured and signed bearer token, and make sure that it has not expired. Learn more about Generating Tokens for API Requests https://developer.apple.com/go/?id=api-generating-tokens 
 ```
 
-**Steps to Resolve the Issue**
+:::info[Prerequisites]
+- Access to your Apple Developer App Store Connect account.
+- Permission to manage API keys under **Users and Access**.
+:::
 
-Follow these steps to generate a new API Key and update it in FlutterFlow:
+**Steps to Resolve the Authentication Error:**
 
-1. Navigate to **App Store Connect**, select **Users and Access**, then select **Keys**.
+1. Open **App Store Connect** and navigate to **Users and Access → Keys**.
 
-2. If visible, click **Request Access**.
+2. If prompted, click **Request Access**.
 
 3. Select **Generate API Key** or click the **Add (+)** button.
 
-4. In the popup window, provide the required API Key information:
-   - **Name**: Enter a reference name for the key.
-   - **Access**: Select the appropriate access type.
+4. In the popup, provide the following details:
+   - **Name**: Enter a descriptive name for the API Key.
+   - **Access**: Choose the appropriate access level for the key.
 
-5. Select **Generate** to create the API Key.
+5. Click **Generate** to create the API Key.
 
-6. Locate the newly created API Key and select **Download API Key**.
+6. Download the newly created API Key by selecting **Download API Key**.
 
    :::note
-   If the **Download API Key** link does not appear immediately, refresh the page.
+   If the download option does not appear immediately, refresh the page.
    :::
 
-7. Return to **FlutterFlow**, navigate to **Settings & Integrations → Deployment**.
-
-8. Under **Private Key**, select **Upload Private Key**, choose the downloaded API Key file, and select **Open**.
+7. In **FlutterFlow**, go to **Settings & Integrations → Deployment**.
 
-9. Attempt to redeploy your app after uploading the new key.
+8. Under **Private Key**, click **Upload Private Key**, select the downloaded API Key file, and click **Open**.
 
-![](../../assets/20250430121336383410.gif)
+9. Retry your iOS deployment.
 
+   ![](../../assets/20250430121336383410.gif)
 
-If the error persists after completing these steps, contact FlutterFlow support via in-app messenger or email at [[email protected]](mailto:[email protected]).
+:::note
+If the error persists after completing these steps, contact FlutterFlow support via in-app messenger or email at [[email protected]](mailto:[email protected]).
+:::

docs/troubleshooting/apple-store-deployment-issues/ios-Signing/download_dsym_file_from_app_store_connect.md

@@ -6,24 +6,30 @@ title: Download dSYM File from App Store Connect
 
 # Download dSYM File from App Store Connect
 
-To download the dSYM file from the App Store Connect Developer Console, follow these steps:
+To download the dSYM file from the App Store Connect Developer Console, follow these steps.
 
-    - **[Sign in](https://appstoreconnect.apple.com/)** to App Store Connect with your Apple Developer account.
-    - Open your app.
-    - Select a build from the **TestFlight** tab on your project page.
-    - Open the **Build Metadata** tab.
-    - Under **Include Symbols**, download your dSYM file.
+:::info[Prerequisites]
+- Access to your Apple Developer account.
+- Your app has at least one build uploaded to App Store Connect.
+:::
+
+**Steps to Download the dSYM File:**
+
+1. **Sign in** to **[App Store Connect](https://appstoreconnect.apple.com/)** with your Apple Developer account.  
+2. Open your app.  
+3. Select a build from the **TestFlight** tab on your project page.  
+4. Open the **Build Metadata** tab.  
+5. Under **Include Symbols**, download the dSYM file.  
 
     ![](../../assets/20250430121257965718.png)
 
-:::note 
-The dSYM file is only available for builds that have been successfully uploaded to App Store Connect and are in a "processing" or "ready for submission" state.
-:::
+    :::note
+    The dSYM file is only available for builds that have been successfully uploaded to App Store Connect and are in a "processing" or "ready for submission" state.
+    :::
 
-    
-If the **Download dSYM file** link is not visible, it indicates that the build submission did not complete successfully. In this case:
+    If the **Download dSYM file** link is not visible, it indicates that the build submission did not complete successfully. In this case:
 
-    - Redeploy the build to the App Store.
-    - After successful processing, return to the Build Metadata tab and download the dSYM file.
+        1. Redeploy the build to the App Store.  
+        2. After successful processing, return to the **Build Metadata** tab and download the dSYM file.  
 
-        ![](../../assets/20250430121258232331.png)
+            ![](../../assets/20250430121258232331.png)

docs/troubleshooting/apple-store-deployment-issues/ios-Signing/imagenotification_development_team_error.md

@@ -8,18 +8,21 @@ title: ImageNotification Development Team Error
 
 This error occurs when the **ImageNotification** entitlement is missing in your Apple Developer account. To resolve it, create a new Identifier for `ImageNotification` in your Apple Developer account.
 
-**Create the Identifier**
+:::info[Prerequisites]
+- Access to your **Apple Developer account**.
+- Permission to manage **Certificates, Identifiers & Profiles**.
+:::
 
-Follow these steps to add the necessary Identifier:
+**Steps to Create the Identifier:**
 
-    1. Sign in to your **[Apple Developer account](https://developer.apple.com/)**.
-    2. Navigate to **Certificates, Identifiers & Profiles**.
-    3. Select **Identifiers**.
-    4. Click the **Add (+)** button.
-    5. Choose **App IDs** and click **Continue**.
-    6. Under **Type**, select **App** and click **Continue**.
-    7. In the **Description** field, enter `ImageNotification` (case-sensitive).
-    8. In the **Bundle ID** field, enter your full bundle ID followed by `.ImageNotification` (for example: `com.example.app.ImageNotification`).
-    9. Click **Continue** and then **Register** to complete the setup.
+1. Sign in to your **[Apple Developer account](https://developer.apple.com/)**.  
+2. Navigate to **Certificates, Identifiers & Profiles**.  
+3. Select **Identifiers**.  
+4. Click the **Add (+)** button.  
+5. Choose **App IDs** and click **Continue**.  
+6. Under **Type**, select **App** and click **Continue**.  
+7. In the **Description** field, enter `ImageNotification` (case-sensitive).  
+8. In the **Bundle ID** field, enter your full bundle ID followed by `.ImageNotification` (for example: `com.example.app.ImageNotification`).  
+9. Click **Continue** and then **Register** to complete the setup.  
 
 Once this Identifier is added, the signing process should proceed without requiring a development team selection.

docs/troubleshooting/apple-store-deployment-issues/publishing/custom_domain_connection_error.md

@@ -3,39 +3,45 @@ keywords: ['configuration', 'connect', 'domain']
 slug: custom-domain-connection-error
 title: Custom Domain Connection Error
 ---
+
 # Custom Domain Connection Error
 
 If you encounter the error shown below after clicking **Connect**, follow these steps to resolve it:
 
 ![](../../assets/20250430121243410633.png)
 
-- **Verify DNS Records**
+:::info[Prerequisites]
+- Access to your domain registrar or DNS provider dashboard.
+- DNS management permissions to add or modify DNS records.
+:::
+
+**Steps to Resolve the Error:**
+
+1. **Verify DNS Records**
 
     - Ensure that you have correctly configured the DNS records required for your custom domain connection.
     - Add the keys provided by FlutterFlow to your domain’s DNS settings.
 
         :::note
-        For A records, if your DNS provider requires a name, you can use **"@"**. When you see an empty value, it typically refers to **"@"**.
+        For A records, if your DNS provider requires a name, you can use `"@"`. When you see an empty value, it typically refers to `"@"`.
         :::
 
         ![](../../assets/20250430121243684493.png)
 
-- **Check for Conflicting Records**
+2. **Check for Conflicting Records**
 
     - Review your DNS configuration to ensure there are no extra or unnecessary records that conflict with the FlutterFlow-provided keys.
-    - For example, if you already have an A record using **"@"**, remove it to avoid conflicts.
+    - For example, if you already have an A record using `"@"`, remove it to avoid conflicts.
 
         :::note
         Before removing any existing DNS records, take screenshots and save them for reference.
         :::
 
-**Example Configurations**
-
-    Below are examples of correct configurations in FlutterFlow and your DNS provider:
 
-    ![](../../assets/20250430121243982678.png)
+        Below are examples of correct configurations in FlutterFlow and your DNS provider:
 
-    ![](../../assets/20250430121244255037.png)
+        ![](../../assets/20250430121243982678.png)
 
-    By following these steps, you can ensure your custom domain is connected correctly.
+        ![](../../assets/20250430121244255037.png)
 
+        By following these steps, you can ensure your custom domain is connected correctly.