updated content, improved formatting, new article titles

Author: mrdavidorok

docs/troubleshooting/apple-store-deployment-issues/Flutter-build-ipa-and-automatic-versioning/how_to_download_dsym_file_from_the_app_store_connect.md

@@ -1,3 +1,3 @@
 {
-  "label": "Apple Store Deployment Issues"
+  "label": "Apple Store Deployment"
 }

docs/troubleshooting/apple-store-deployment-issues/Flutter-build-ipa-and-automatic-versioning/what_to_do_when_sign_in_for_imagenotification_requires_a_development_team.md

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

docs/troubleshooting/apple-store-deployment-issues/_category_.json

@@ -0,0 +1,63 @@
+---
+keywords: ['deployment', 'flutter', 'exited']
+slug: /codemagic-install-pods-failure
+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.
+
+## Custom Code Package Conflicts
+
+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.
+
+**Solution:**
+
+  - 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.
+
+    For example, the package `platform_device_id` may cause conflicts:
+
+    ![](../../assets/20250430121132533922.png)
+
+## Deployment from an Incompatible GitHub Branch
+
+Deploying from a GitHub branch that contains untested custom code or recent dependency changes may result in deployment failures.
+
+  **Solution:**
+
+    - 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.
+
+      For example, the branch `dungtienle/folhavpnV3` may contain unstable code:
+
+      ![](../../assets/20250430121132883140.png)
+
+    - Review recent commits to identify and address changes affecting pod installation.
+    - Revert problematic commits if necessary.
+
+## Incompatible Pod Versions
+
+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.

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

@@ -0,0 +1,36 @@
+---
+keywords: ['signing', 'codemagic', 'certificate']
+slug: /codemagic-signing-certificate-limit
+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.
+
+**Full 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.
+```
+
+This error indicates that Codemagic cannot create a new certificate because existing certificates or pending certificate requests are already using the available slots.
+
+**Solution**
+
+To resolve this issue, delete unused distribution certificates from your Apple Developer account to free up space for new certificates.
+
+    **Steps to Delete 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**.
+
+    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.
+    :::
+
+