Typo fixed, improved formatting, assets added

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

@@ -0,0 +1,27 @@
+---
+keywords: ['connect', 'download', 'store']
+slug: /how-to-download-dsym-file-from-the-app-store-connect
+title: How to download dSYM file from the app store connect?
+---
+# How to download dSYM file from the app store connect?
+
+To download the dSYM file from the App Store Connect Developer Console, follow these steps:
+
+- [Sign in](https://appstoreconnect.apple.com/) in to the App Store Connect Developer Console with your Apple Developer account.
+
+- Open your app
+
+- Select a build from the test flight tab on your project page
+
+- Open the Build Metadata tab
+    Now you should be able to see the Include symbols part and download your dSYM file​
+
+![](../../assets/20250430121257965718.png)
+
+:::note 
+You will only be able to download the dSYM file for builds that have been successfully uploaded to App Store Connect and are in a "processing" or "ready for submission" state. 
+:::
+
+If you can't see the Download dSYM file link, then seems there was an issue during the deployment to the app store. You need to deploy again. After the submission proceeds, you can again try to download the file.​
+
+![](../../assets/20250430121258232331.png)

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,24 @@
+---
+keywords: ['requires', 'sign', 'team']
+slug: /what-to-do-when-sign-in-for-imagenotification-requires-a-development-team
+title: What To Do When Sign In for "ImageNotification" Requires a Development Team
+---
+
+# What To Do When Sign In for "ImageNotification" Requires a Development Team
+
+To resolve this issue, you’ll need to create an Identifier on [developer.apple.com](https://developer.apple.com/) called: `[yourbundleID].ImageNotification`.
+
+## Adding the Identifier
+You must add an Identifier to be able to send push notifications to iOS devices after you deploy your app to the App Store.
+
+### Steps to Add an Identifier
+
+1. From your **Apple Developer account**, open the **Identifiers** section.
+2. Click on the **(+)** button on the right side of the **Identifiers** label.
+3. Select **App IDs** and click **Continue**.
+4. Select the *Type* **App** and click **Continue**.
+5. Enter the **Description** as `ImageNotification` (make sure to use the exact same letters and capitalization: `ImageNotification`).
+6. Enter the **Bundle ID** as your package name and add `.ImageNotification` at the end.
+7. Click **Continue** and then click **Register**.
+
+

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

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

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

@@ -0,0 +1,59 @@
+---
+keywords: ['authentication', 'deployment', 'ios']
+slug: /codemagic-deployment-on-ios-authentication-credentials-are-missing-or-invalid
+title: 'Codemagic Deployment on iOS: Authentication Credentials Are Missing or Invalid'
+---
+# Codemagic Deployment on iOS: Authentication Credentials Are Missing or Invalid
+
+If you need help identifying your Codemagic deployment error then check out this article. 
+
+## Invalid Authentication Credentials Error
+
+This means that there was a misconfiguration issue while setting up deployment for App Store. The token used is likely expired or is invalid. 
+
+Learn more about Generating Tokens for API Requests by clicking [here](https://developer.apple.com/go/?id=api-generating-tokens)
+
+
+### Full error message
+
+```
+Failed Step: Fetch signing filesGET 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 
+```
+
+## How To Resolve the Issue
+
+To resolve this issue, you'll need to generate a new API key for your app and then replace it with the one present inside FlutterFlow. 
+
+Please follow these steps to generate your API Key:
+
+- Navigate to App Store Connect, select **Users and Access**, and then select **Keys** (*blue text*).
+
+- If you see the **Request Access** button, click on it.
+
+- Click on the **Generate API Key**. Otherwise, select the **Add button (+).**
+
+- A popup will appear. Enter your API Key Information:
+
+    - **Name**: Enter a name for the key. This is a reference and is not part of the key itself.
+
+    - **Access**: Select the access type. This link has additional information on roles.
+
+- When you are done, select **Generate.**
+
+- Find the row for the API Key you just generated and select **Download API Key**. A popup will appear, select **Download**​
+
+:::note
+If you don't see the Download API Key link immediately, refresh your page.
+:::
+
+- Return to FlutterFlow and navigate to **Settings & Integrations **--> **Deployment**
+
+- Under **Private Key, **select** Upload Private Key. **Select the **API Key File **and then select **Open.**
+
+After this please try deploying the app again. 
+
+![](../../assets/20250430121336383410.gif)
+
+## Still need help? 
+
+If you are deploying from FlutterFlow and still getting this error after following all the steps outlined above, then please report this issue to support via messengar or email at [email protected].​

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

@@ -0,0 +1,90 @@
+---
+keywords: ['deployment', 'flutter', 'exited']
+slug: /codemagic-deployment-step-6-script-install-pods-exited-with-status-code-1
+title: 'Codemagic Deployment: Step 6 Script ''Install Pods'' Exited with Status Code
+  1'
+---
+
+# Codemagic Deployment: Step 6 Script 'Install Pods' Exited with Status Code 1
+
+When Codemagic's deployment fails at the 'Install Pods' step, the root cause is usually related to dependency management in iOS builds. Here’s how to tackle each issue specifically.​
+
+## Scenario 1: Custom Code Package Conflicts
+
+### What is the issue? 
+The deployment process is hindered by a conflict between custom code packages and the existing packages in the project.​
+
+### Why does this happen?
+Dependencies in Flutter projects have version constraints that must be compatible with each other. When a new package is introduced, or when versions are updated without checking for compatibility, it may lead to conflicts that prevent pods from installing correctly.​
+
+### How can you fix it?
+Adjust the versions of the conflicting packages. This could mean either downgrading to a version that plays well with other dependencies or, in some cases, upgrading to a newer version that has resolved these conflicts.
+
+​Example & Solution: 
+In the provided example, `platform_device_id` could be causing the issue. A potential fix would be to:​
+
+![](../../assets/20250430121132533922.png)
+
+- Check the package's documentation for known compatibility issues.
+
+- Modify **`pubspec.yaml`** to use a version that’s known to be compatible.
+
+- Run **`flutter pub get`** to update the dependencies accordingly.
+
+## Scenario 2: Deployment Directly from an Incompatible GitHub Branch
+
+### What is the issue?
+
+A GitHub branch being used for deployment may contain custom codes or dependency changes that haven't been fully tested for compatibility, leading to deployment failures.
+
+### Why does this happen?
+Branches often have experimental or in-progress work that may not be stable. When these branches are deployed without thorough testing, incompatibilities or errors can arise.
+
+### ​How can you fix it?
+- Ensure that the branch you're deploying from is stable and has been tested. You might need to:
+
+- Merge the latest stable changes into your deployment branch.
+
+- Remove any experimental or untested code that could be causing the issues.
+
+Example & Solution:
+
+The second image suggests that the GitHub repo `dungtienle/folhavpnV3` might have unstable code. To remedy this, one should:
+
+![](../../assets/20250430121132883140.png)
+
+- Check out a stable branch that is known to be working correctly.
+
+- Review recent commits on the problematic branch to identify any changes that might affect pod installation.
+
+- Revert to a commit before the changes or fix the issues before retrying the deployment.
+
+## Scenario 3: Incompatible Pod Versions
+
+### What is the issue?
+CocoaPods, the dependency manager for Swift and Objective-C Cocoa projects, cannot find compatible versions for a specific pod, which in this case, is `app_settings`.
+
+### Why does this happen?
+This problem typically occurs when the Podfile specifies a version of a pod that isn't compatible with the other pods or with the minimum iOS deployment target.
+
+### How can you fix it?
+You can either downgrade the problematic package to a compatible version or upgrade the iOS minimum deployment target. For the latter, this would require downloading the Flutter project and manually adjusting the deployment target in Xcode.
+
+​Example & Solution: 
+The engineering team identified `app_settings` as a culprit. To resolve this, follow these steps:
+
+![](../../assets/20250430121133219967.png)
+
+- Change the version of **`app_settings`** in **`pubspec.yaml`** to one that’s known to be compatible.
+
+- If that doesn’t work, increase the minimum iOS deployment target as suggested by the Amplify Docs on Flutter platform setup.
+
+## Key Points to Remember
+
+- Always check for the compatibility of new packages or versions with the existing project dependencies.
+
+- Deploy from stable, tested branches rather than branches with experimental features.
+
+- Consider the minimum deployment target requirements when troubleshooting pod installation issues.
+
+By carefully examining these scenarios and applying the appropriate fixes, you can overcome the 'Install Pods' error and continue with a successful deployment in FlutterFlow using Codemagic.

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

@@ -0,0 +1,30 @@
+---
+keywords: ['signing', 'error', 'fetch']
+slug: /error-step-3-script-fetch-signing-files-exited-with-status-code-1-you-already-have-a-current-distribution-certificate-or-a-pending-certificate-request
+title: 'Error: Step 3 script `Fetch signing files` exited with status code 1. You
+  already have a current Distribution certificate or a pending certificate request.'
+---
+# Error: Step 3 script `Fetch signing files` exited with status code 1. You already have a current Distribution certificate or a pending certificate request.
+
+## What does this error mean?
+During deployment, Codemagic tried to create distribution certificates in your Apple Console. This failed as you have reached the maximum number of allowed certificates in the Apple Console.
+
+## 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.
+```
+## How to resolve this issue?
+You need to delete a few distribution certificates so that the build can go through.​
+
+## Steps to delete:
+
+- Open the Apple Developer Console in App Store Connect
+
+- Select 'Keychain>Login' , then 'Category>My Certificates
+
+- Locate and delete your developer, distribution. and server certificates (if applicable)
+
+:::note 
+These certificates are used for signing the application and will be created on-demand during the build.
+:::

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

@@ -0,0 +1,34 @@
+---
+keywords: ['configuration', 'connect', 'domain']
+slug: /can-not-connect-my-custom-domain
+title: Can not connect my custom domain.
+---
+# Cannot connect my custom domain.
+
+![](../../assets/20250430121243410633.png)
+
+If you face this error after clicking Connect then do the following:
+
+- Make sure you did configure the domain DNS records we need before try to connect.
+
+- Make sure you create the keys Flutterflow provides to you in your domain DNS configurations.
+
+:::note
+For the A record, in your DNS configuration if the name was required you can use "@". when you see the value is empty in terms of these kinds of keys it means the value in "@"​
+:::
+
+![](../../assets/20250430121243684493.png)
+
+- Make sure in your DNS configuration there is no unnecessary or extra key that has conflicts with the Flutterflow keys.
+
+Example:  you have another A record, with the same value "@" in your DNS record you need to remove it
+
+:::note 
+Before removing any key make sure you screenshot the keys and save them somewhere in your device.
+:::
+
+Here is an example of a configuration in Flutterflow and DNS.​
+
+![](../../assets/20250430121243982678.png)
+
+![](../../assets/20250430121244255037.png)​

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

@@ -0,0 +1,25 @@
+---
+keywords: ['faqs', 'publishing', 'flutterflow']
+slug: /faqs-on-web-publishing-in-flutterflow
+title: FAQs on Web Publishing In FlutterFlow
+---
+# FAQs on Web Publishing In FlutterFlow
+
+Below are some of the most commonly asked questions about Web Publishing in FlutterFlow.
+
+---
+
+## Question: 
+
+Which certifications does FlutterFlow’s web server (which hosts our web application) have?
+
+Answer: FlutterFlow web hosting runs on Google Compute Engine. More details on compliance and certification are available here: [Google Cloud Compliance](https://cloud.google.com/security/compliance)
+
+
+## Question: 
+
+What are the system requirements to have a FlutterFlow web application code running on our own server? (E.g. NodeJS? PHP? Apache Web Server?)
+
+Answer: The code exported from FlutterFlow is regular Flutter code. You can find out about compiling and hosting Flutter apps here: [Flutter Web Deployment Guide](https://docs.flutter.dev/deployment/web)
+
+In general, compiled Flutter projects are static content which can be hosted on most web servers.

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

@@ -0,0 +1,88 @@
+---
+keywords: ['error', 'custom', 'domains']
+slug: /publishing-custom-domains-in-flutterflow
+title: Publishing Custom Domains in FlutterFlow
+---
+# Publishing Custom Domains in FlutterFlow
+
+Having trouble connecting your custom domain in FlutterFlow? In this article, we've outlined some common issues users face and step-by-step solutions to get you back on track.
+
+## Issue: 
+Unable to Connect Custom Domain (Error: Expected DNS records not found)
+
+Scenario:
+You've set up the DNS records for your domain, but the connection still fails.
+
+:::tip
+Misconfigured DNS is often the culprit.
+:::
+
+## Background: 
+FlutterFlow requires specific DNS records for custom domain connection, and you should set them according to your domain. Here's where you'll find them:
+
+![](../../assets/20250430121150348694.png)
+
+:::note 
+If you uncheck **“Also www...”** you won’t need to create the second, **CNAME** record.​
+:::
+
+## Troubleshooting Steps:
+
+### Verify DNS Records:
+Use tools like nslookup.io to check your DNS records against the required configuration.
+Ensure the required A and CNAME records exist. No other A, AAAA, or CNAME records should interfere. Here's an example:
+
+![](../../assets/20250430121150651702.png)
+
+### Wait Period: 
+DNS changes may take up to 24 hours to generate. Please wait at least an hour after making changes before retrying.
+
+### Retry: 
+If records are correct, retry connecting after some time.​
+
+### Reach out to support: 
+If all the settings are correct and you are still facing the issue after 48 hours, please communicate with the domain registrar.
+
+## Issue: 
+Difficulty Creating DNS Records
+
+:::tip
+Each registrar may have a different interface, complicating the process.***
+:::
+
+## Suggestions:
+
+- When you create a record for a root domain, e.g. example.com, some registrars require the “name” field for the record to be empty, some require “@”, and some - a full domain name (example.com).
+
+- When they create a record for a subdomain, e.g. test.example.com, some registrars require the “name” field for the record to be the name of the subdomain (”test”), some - full name (test.example.com).
+
+Please refer to Registrar-specific documentation to learn more about how you can set up the DNS records.
+
+## Issue: 
+Error 404 After Connecting Domain
+
+## Solution:
+
+Please try publishing the project after connecting the domain, it should resolve the issue that you are experiencing regarding Error 404.
+
+## DNS Restrictions for SSL Certificates
+
+### Background: 
+The DNS might be restricting the SSL certificate authorities, which results in an error while connecting the domain.​
+
+### Solution: 
+
+- Verification:
+Use nslookup.io to check for CAA records. you should be able to check that using this link: https://www.nslookup.io/domains/your-site-name/dns-records/caa/. consider replacing "your-site-name" with your site.
+
+- Adjustment:
+Add "letsencrypt.org" to allow authorities or remove CAA records.
+
+- Outcome:
+FlutterFlow should connect once DNS is adjusted.
+
+By following these steps, you can troubleshoot and resolve common issues encountered when connecting a custom domain in FlutterFlow. If you still face challenges, don't hesitate to reach out to our support team through Live chat or by emailing [email protected]
+
+
+
+