fixed all internal links

mrdavidorok · mrdavidorok · commit a4379be62404 · 2025-06-16T14:26:00.000+01:00
diff --git a/docs/troubleshooting/deployment/codemagic_deployment_error_identification.md b/docs/troubleshooting/deployment/codemagic_deployment_error_identification.md
@@ -5,7 +5,7 @@ title: Codemagic Deployment Error Identification
 ---
 # Codemagic Deployment Error Identification
 
-## How to Identify Your Codemagic Error
+**Identifying Errors in Codemagic**
 
 Follow the steps below to identify your codemagic error:
 
@@ -29,9 +29,7 @@ Follow the steps below to identify your codemagic error:
 
 - Now, press **Cmd/Ctrl + F** to search for the term **"error"** in the logs to find the root cause of the issue. Keep pressing **"Enter"** till you find the error ( this is usually at the bottom of the logs ).
 
-  If you search for "error" and still don't find an error message that makes sense to you then you can also try with the following keyword:
-    
-    **message**
+  If you search for "error" and still don't find an error message that makes sense to you then you can also try with the following keyword "message".
 
     ![](../assets/20250430121347925706.png)
 
diff --git a/docs/troubleshooting/deployment/codemagic_deployment_tips.md b/docs/troubleshooting/deployment/codemagic_deployment_tips.md
@@ -8,7 +8,7 @@ title: CodeMagic Deployment Tips
 Here are some tips to avoid Deployment issues:
 
 :::tip
-- Make sure you've followed all the steps for [setting up deployment](/deployment/deploy-for-environments/#mobile-deployment) in your project.
+- Make sure you've followed all the steps for **[setting up deployment](/deployment/deploy-for-environments/#mobile-deployment)** in your project.
 - If you choose a deployment source from a GitHub Repository then please make sure that it's associated with FlutterFlow's GitHub integration.
 - If you are deploying to the Play Store from a GitHub repo, make sure to modify your build.gradle file to sign in release mode.
 - Setting a version number is optional but may be required for specific cases. If you are updating an existing app that has not been deployed using FlutterFlow yet, you will want to specify a version number.
diff --git a/docs/troubleshooting/deployment/deployment_issues_with_stripe_integration.md b/docs/troubleshooting/deployment/deployment_issues_with_stripe_integration.md
@@ -9,11 +9,11 @@ Integrating Stripe in your FlutterFlow project can help you accept payments effi
 
 1. **Firebase Connection**
 
-    Stripe integration requires a connected Firebase project. Before running through this checklist, it's important to ensure your FlutterFlow project is linked to Firebase, a crucial step for successful payment processing. Detailed guidance can be found at [FlutterFlow's Firebase Setup Guide](https://docs.flutterflow.io/data-and-backend/firebase/firebase-setup).
+    Stripe integration requires a connected Firebase project. Before running through this checklist, it's important to ensure your FlutterFlow project is linked to Firebase, a crucial step for successful payment processing. Detailed guidance can be found at **[FlutterFlow's Firebase Setup Guide](/integrations/firebase/connect-to-firebase/#step-1-set-up-your-project)**.
 
 2. **Upgrade to Firebase Blaze Plan**
 
-    Stripe functionality requires a Firebase Blaze Plan for operational capabilities. To avoid disruptions, you will need to upgrade from the Firebase Spark plan to the Blaze plan. Learn more about Google's process for upgrading [here](https://firebase.google.com/docs/projects/billing/firebase-pricing-plans).
+    Stripe functionality requires a Firebase Blaze Plan for operational capabilities. To avoid disruptions, you will need to upgrade from the Firebase Spark plan to the Blaze plan. Learn more about **[Google's process for upgrading](https://firebase.google.com/docs/projects/billing/firebase-pricing-plans)**.
 
 3. **Set the Google Cloud Platform (GCP) Location**
 
@@ -23,13 +23,13 @@ Integrating Stripe in your FlutterFlow project can help you accept payments effi
 
 4. **Firebase Project Permissions**
 
-    Ensure you have the necessary permissions enabled for your Firebase project. Two critical permissions involve access management and service configuration. You can reference the [setup guide](https://docs.flutterflow.io/data-and-backend/firebase/firebase-setup)on FlutterFlow Documentation on FlutterFlow Documentation.​
+    Ensure you have the necessary permissions enabled for your Firebase project. Two critical permissions involve access management and service configuration. You can reference the **[setup guide](/integrations/firebase/connect-to-firebase/#step-1-set-up-your-project)** on FlutterFlow Documentation on FlutterFlow Documentation.​
 
     ![](../assets/20250430121122068343.png)
 
 5. **Correct Merchant Code**
 
-    Use the correct 3-letter merchant country code (e.g., "GBR" for the United Kingdom vs. "UK"). Incorrect codes can lead to failed transactions. For accurate codes, refer to [IBAN Country Codes](https://www.iban.com/country-codes).​
+    Use the correct 3-letter merchant country code (e.g., "GBR" for the United Kingdom vs. "UK"). Incorrect codes can lead to failed transactions. For accurate codes, refer to **[IBAN Country Codes](https://www.iban.com/country-codes)**.​
 
     ![](../assets/20250430121122307123.png)
     
diff --git a/docs/troubleshooting/deployment/fixing_razorpay_deployment.md b/docs/troubleshooting/deployment/fixing_razorpay_deployment.md
@@ -5,7 +5,7 @@ title: Fixing Razorpay Deployment
 ---
 # Fixing Razorpay Deployment
 
-Razorpay is a major payment processor in India. Integrating [Razorpay](https://razorpay.com/) can allow users to make payments using their app. This article outlines some common scenarios and troubleshooting instructions for Razorpay deployment issues.
+Razorpay is a major payment processor in India. Integrating **[Razorpay](https://razorpay.com/)** can allow users to make payments using their app. This article outlines some common scenarios and troubleshooting instructions for Razorpay deployment issues.
 
 1. **Firebase Integration and Auth**
 
@@ -28,7 +28,7 @@ Razorpay is a major payment processor in India. Integrating [Razorpay](https://r
 
 4. **Firebase Project Permissions**
 
-    Make sure your Firebase project has the required permissions activated. Access management and service configuration are two essential permissions to focus on. For guidance on setting these up, look at the instructions in the [FlutterFlow Project Setup](https://docs.flutterflow.io/resources/projects/settings/project-setup/).
+    Make sure your Firebase project has the required permissions activated. Access management and service configuration are two essential permissions to focus on. For guidance on setting these up, look at the instructions in the **[FlutterFlow Project Setup](/resources/projects/settings/project-setup/)**.
 
 5. **Razorpay Keys Check**
 
diff --git a/docs/troubleshooting/deployment/fixing_stripe_deployment_and_payment_errors.md b/docs/troubleshooting/deployment/fixing_stripe_deployment_and_payment_errors.md
@@ -11,11 +11,11 @@ Integrating Stripe for payment processing in FlutterFlow can significantly simpl
 
 1. **Firebase Connection**
 
-    Stripe integration requires a connected Firebase project. Before running through this checklist, it's important to ensure your FlutterFlow project is linked to Firebase, a crucial step for successful payment processing. Detailed guidance can be found at [FlutterFlow's Firebase Setup Guide](https://docs.flutterflow.io/data-and-backend/firebase/firebase-setup).
+    Stripe integration requires a connected Firebase project. Before running through this checklist, it's important to ensure your FlutterFlow project is linked to Firebase, a crucial step for successful payment processing. Detailed guidance can be found at **[FlutterFlow's Firebase Setup Guide](/integrations/firebase/connect-to-firebase/)**.
 
 2. **Upgrade to Firebase Blaze Plan**
 
-    Stripe functionality requires a Firebase Blaze Plan for operational capabilities. To avoid disruptions, you will need to upgrade from the Firebase Spark plan to the Blaze plan. Learn more about Google's process for upgrading [here](https://firebase.google.com/docs/projects/billing/firebase-pricing-plans).
+    Stripe functionality requires a Firebase Blaze Plan for operational capabilities. To avoid disruptions, you will need to upgrade from the Firebase Spark plan to the Blaze plan. Learn more about **[Google's process for upgrading](https://firebase.google.com/docs/projects/billing/firebase-pricing-plans)**.
 
 3. **Set the Google Cloud Platform (GCP) Location**
 
@@ -25,13 +25,14 @@ Integrating Stripe for payment processing in FlutterFlow can significantly simpl
 
 4. **Firebase Project Permissions**
 
-    Ensure you have the necessary permissions enabled for your Firebase project. Two critical permissions involve access management and service configuration. You can reference the [setup guide](https://docs.flutterflow.io/data-and-backend/firebase/firebase-setup) on FlutterFlow Documentation.​
+    Ensure you have the necessary permissions enabled for your Firebase project. Two critical permissions involve access management and service configuration. You can reference the **[setup guide](/integrations/firebase/connect-to-firebase/)**
+ on FlutterFlow Documentation.​
 
     ![](../assets/20250430121145949036.png)
 
 5. **Correct Merchant Code**
 
-    Use the correct 3-letter merchant country code (example., "GBR" for the United Kingdom vs. "UK"). Incorrect codes can lead to failed transactions. For accurate codes, refer to [IBAN Country Codes](https://www.iban.com/country-codes).​
+    Use the correct 3-letter merchant country code (example., "GBR" for the United Kingdom vs. "UK"). Incorrect codes can lead to failed transactions. For accurate codes, refer to **[IBAN Country Codes](https://www.iban.com/country-codes)**.​
 
     ![](../assets/20250430121146161973.png)
     
diff --git a/docs/troubleshooting/deployment/resolve_errors_in_downloaded_code.md b/docs/troubleshooting/deployment/resolve_errors_in_downloaded_code.md
@@ -29,7 +29,7 @@ When you download your project from FlutterFlow and run it locally in your IDE,
 
 3. **Upgrading or Downgrading to the correct Flutter version**
 
-    If the current version on your machine is different than what is currently supported by FlutterFlow, you can downgrade or upgrade to the supported version. You can learn more about [**upgrading Flutter**](https://docs.flutterflow.io/deploying-your-app/testing-your-app/testing-on-mobile-device#id-2.-verify-correct-flutter-version). ​By following these steps, you can fix the errors that you face after downloading the code and run locally. 
+    If the current version on your machine is different than what is currently supported by FlutterFlow, you can downgrade or upgrade to the supported version. You can learn more about [**upgrading Flutter**](/testing/local-run/#4-running-app-on-device). ​By following these steps, you can fix the errors that you face after downloading the code and run locally. 
 
 If you continue to experience issues, contact the FlutterFlow support team via live chat or email at support@flutterflow.io.
 

-Original file line number
+Diff line change
 . **Upgrading or Downgrading to the correct Flutter version**
 -    If the current version on your machine is different than what is currently supported by FlutterFlow, you can downgrade or upgrade to the supported version. You can learn more about [**upgrading Flutter**](https://docs.flutterflow.io/deploying-your-app/testing-your-app/testing-on-mobile-device#id-2.-verify-correct-flutter-version). By following these steps, you can fix the errors that you face after downloading the code and run locally.
 +    If the current version on your machine is different than what is currently supported by FlutterFlow, you can downgrade or upgrade to the supported version. You can learn more about [**upgrading Flutter**](/testing/local-run/#4-running-app-on-device). By following these steps, you can fix the errors that you face after downloading the code and run locally.
 If you continue to experience issues, contact the FlutterFlow support team via live chat or email at [email protected].