Google Play Store Deployment Issues: Typos fixed, assets added, formatting adjusted

docs/troubleshooting/google-play-store-deployment-issues/_category_.json

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

docs/troubleshooting/google-play-store-deployment-issues/failed-step-build-aab-with-flutter/_category_.json

@@ -0,0 +1,3 @@
+{
+  "label": "Android Build Errors"
+}

docs/troubleshooting/google-play-store-deployment-issues/failed-step-build-aab-with-flutter/you_uploaded_an_apk_or_android_app_bundle_that_was_signed_in_debug_mode..md

@@ -0,0 +1,42 @@
+---
+keywords: ['debug', 'android', 'release']
+slug: /signed-in-debug-mode-error
+title: Signed in Debug Mode Error
+---
+# Signed in Debug Mode Error.
+
+:::info[Prerequisites]
+
+Before proceeding, ensure that you:
+
+- Have generated an APK or Android App Bundle via **FlutterFlow → Build → Android**.
+- Have access to your exported project folder.
+- Are able to edit the **android/app/build.gradle** file.
+
+:::
+
+When uploading your Android APK or App Bundle to the Play Store or any production environment, you may encounter the following error:
+
+```
+You uploaded an APK or Android App Bundle that was signed in debug mode. You need to sign your APK or Android App Bundle in release mode
+```
+
+This happens when your build is signed using a **debug configuration**, which is not acceptable for release uploads.
+
+This means that your current build is using the **debug** signing config, which is meant for internal testing or development only.  
+To fix this, you must update your **build.gradle** file and use the **release** signing configuration.
+
+
+Follow the steps below to update your configuration:
+
+- Step 1: Find the debug keyword under buildTypes in android/app/builld.gradle in your project folder
+
+    ![](../../assets/20250430121331806679.png)
+
+- Step 2: Replace the debug keyword with release and then save the file
+
+    ![](../../assets/20250430121332062568.png)
+
+
+
+If this does not resolve the issue, contact FlutterFlow Support at [email protected]

docs/troubleshooting/google-play-store-deployment-issues/failed-step-generate-launch-icon/_category_.json

@@ -0,0 +1,3 @@
+{
+  "label": "Generate Launch Icon"
+}

docs/troubleshooting/google-play-store-deployment-issues/failed-step-generate-launch-icon/fix_launcher_icons_package_error.md

@@ -0,0 +1,76 @@
+---
+keywords: ['error', 'package', 'icon']
+slug: /fix-launcher-icons-package-error
+title: Fix Flutter Launcher Icons Package Error
+---
+
+:::info[Prerequisites]
+
+Before you begin, ensure that:
+
+- You have access to your FlutterFlow project.
+- You can open and edit your **pubspec.yaml** file.
+- You are familiar with your build environment (FlutterFlow, GitHub, or IDE).
+:::
+
+When building your app, you may encounter the following error:
+
+```js
+Codemagic Deploy Output Failed Step: Generate Launch Icon Could not find package "flutter_launcher_icons". Did you forget to add a dependency? pub finished with exit code 65. Build failed: Step 5 script 'Generate Launch Icon' exited with status code 65. 
+```
+
+This error means that the required **flutter_launcher_icons** package is missing or not properly configured.
+
+If the error is caused by fix build error in FlutterFlow then do the following:
+
+- **Clear and Reset App Assets**
+
+    - Navigate to **Settings and Integrations > App Assets** inside FlutterFlow.
+    - If the **Splash Screen** and **Launcher Icon** are already set:
+        - Clear both.
+        - Re-upload the launcher icons.
+
+    ![](../../assets/20250430121327988277.gif)
+
+
+If the error is caused by fix build error in GitHub Deployment then do the following:
+
+**Add flutter_launcher_icons package to pubspec.yaml**
+
+Open your **pubspec.yaml** file and add the following under **dev_dependencies**:
+
+    ```yaml
+    dev_dependencies:
+        flutter_launcher_icons: "^0.10.0"
+
+    flutter_icons:
+    android: true
+    ios: true
+    image_path_ios: "assets/images/launcher/ios.png"
+    image_path_android: "assets/images/launcher/android.png"
+    ```
+
+    Explanation:
+
+        - flutter_launcher_icons: "^0.10.0": Specifies the version of the launcher icons package.
+        - image_path_ios: Path to the iOS launcher icon image.
+        - image_path_android: Path to the Android launcher icon image.
+    Ensure your image files exist at the correct paths.
+
+    After adding the package, run the following commands in your terminal or IDE:
+
+    ```bash
+    flutter pub get
+    flutter pub run flutter_launcher_icons:main
+    flutter run
+    ```
+
+        - flutter pub get: Fetches all required packages.
+        - flutter pub run flutter_launcher_icons:main: Generates launcher icons.
+        - flutter run: Builds and runs the app.
+
+    If this does not resolve the issue, contact FlutterFlow Support at [email protected] for further assistance.
+
+
+
+

docs/troubleshooting/google-play-store-deployment-issues/failed-step-generate-launch-icon/launcher_icon_missing_after_upload.md

@@ -0,0 +1,29 @@
+---
+keywords: ["icon", "added", "launcher"]
+slug: /launcher-icon-missing-after-upload
+title: Launcher Icon Missing After Upload
+---
+
+# Launcher Icon Missing After Upload
+
+If your custom app launcher icon is not appearing after adding it in the project settings, follow these steps to resolve the issue:
+
+1. **Run the Launcher Icon Generation Command**
+
+    After downloading or exporting your code, open a terminal in your project directory and run:
+
+    ```sh
+    flutter pub run flutter_launcher_icons:main
+    ```
+
+    This command will generate the launcher icons for your app.
+
+2. **Set Up Your Flutter Environment**
+
+    To run the above command, you need to have a Flutter environment set up on your machine. Follow the official **[Flutter installation guide](https://docs.flutter.dev/get-started/install)** if you haven't already.
+
+:::info[Still not working?]
+- Double-check that your icon files are correctly named and placed in the appropriate directory.
+- Make sure your `pubspec.yaml` includes the correct configuration for `flutter_launcher_icons`.
+- Try cleaning your project with `flutter clean` and then re-running the icon generation command.
+:::

docs/troubleshooting/google-play-store-deployment-issues/failed-step-get-flutter-packages/_category_.json

@@ -0,0 +1,3 @@
+{
+  "label": "Get Flutter Packages"
+}

docs/troubleshooting/google-play-store-deployment-issues/failed-step-get-flutter-packages/i_get_this_error_error_running_pod_install.md

@@ -0,0 +1,30 @@
+---
+keywords: ['error', 'running', 'install']
+slug: /error-running-pod-install
+title: Error Running Pod Install
+---
+
+# Error Running Pod Install
+
+If you see the error **"Error running pod install"**, it usually means there is a misconfiguration of Flutter on your device.
+
+Follow the steps below to fix the issue: 
+
+  - Make sure Flutter is set up correctly on your device. Follow the official guide: **[Flutter - Get Started: Install on macOS](https://docs.flutter.dev/get-started/install/macos)**
+  - If you are on a Mac, see this article for troubleshooting: **[Troubleshooting Flutter on macOS](https://intercom.help/flutterflow/en/articles/6156947-i-get-this-error-error-running-pod-install)**
+
+:::tips[Additional Tips]
+- Run `flutter doctor` in your terminal to check for any missing dependencies or issues.
+- Make sure CocoaPods is installed and up to date by running:
+  ```sh
+  sudo gem install cocoapods
+  pod repo update
+  ```
+- If you continue to have issues, try deleting the `ios/Pods` directory and the `ios/Podfile.lock` file, then run:
+  ```sh
+  flutter clean
+  flutter pub get
+  cd ios
+  pod install
+  ```
+:::

docs/troubleshooting/google-play-store-deployment-issues/failed-step-get-flutter-packages/version_solving_failed_due_to_incompatible_package.md

@@ -0,0 +1,23 @@
+---
+keywords: ['error', 'version', 'failed']
+slug: /version-solving-failed-due-to-incompatible-package
+title: Version Solving Failed Due to Incompatible Package.
+---
+# Version Solving Failed Due to Incompatible Package.
+
+When running `flutter pub get`, you may encounter a **version solving failed** error if your project contains package versions that are incompatible with FlutterFlow’s supported Flutter version. 
+
+```js
+Running "flutter pub get" in flutter_tools... 3.4s Resolving dependencies... Because every version of flutter_test from sdk depends on collection 1.15.0 and horse_care_new depends on collection 1.16.0, flutter_test from sdk is forbidden. So, because horse_care_new depends on flutter_test from sdk, version solving failed. pub finished with exit code 1
+```
+
+Follow the steps below to solve the issue:
+
+    If you are using a custom action/widget in your project.
+
+    - Check if the package you use for custom action or widget is compatible with FlutterFlow's Flutter version.
+
+    - Check the pubspec.yaml file before adding the dependency to the custom widget/action so that if the package already exists in pubspec file, then you only need to add it as a header file in the custom widget/action code. You won't need to add the dependency separately.
+
+    If you aren't using any custom widget or action, then please report this issue to support via Chat or Email at [email protected].
+

docs/troubleshooting/google-play-store-deployment-issues/failed-step-publishing/_category_.json

@@ -0,0 +1,3 @@
+{
+  "label": "Publishing"
+}

docs/troubleshooting/google-play-store-deployment-issues/failed-step-publishing/admob_ad_display_issues_in_open_testing_on_google_play_store.md

@@ -0,0 +1,58 @@
+---
+keywords: ['testing', 'configuration', 'display']
+slug: /admob-ads-not-displaying-in-google-play-testing
+title: AdMob Ads Not Displaying in Google Play Testing
+---
+# AdMob Ads Not Displaying in Google Play Testing
+
+:::info[Prerequisites]
+Before you proceed, ensure:
+
+- You have an active **AdMob** account.
+- Your app is properly linked to **AdMob**.
+- Your app is uploaded to **Google Play Console** under Open Testing.
+:::
+
+If your AdMob ads are not displaying during Open Testing on the **Google Play Store**, this may be due to configuration issues or missing approvals.
+
+---
+
+**Use Test Ads During Testing**
+
+    When testing your app, always use **test ads** to avoid policy violations or issues during the testing phase. **Live ads** are designed to function primarily in production.
+
+    For more information, refer to **[Google AdMob Test Ads](https://developers.google.com/admob/android/test-ads)**.
+
+
+**Verify AdMob Account Configuration**
+
+    Check that:
+
+        - Your app is correctly registered in **AdMob**.
+        - The app’s release status in AdMob reflects its actual status on **Google Play Console**.
+
+    If your app is marked as **not released** in AdMob, live ads may not appear during testing.
+
+**Declare Advertising ID in Google Play Console**
+
+    For apps targeting **Android 13 (API 33)** or higher:
+
+        1. Navigate to your app in **Google Play Console**.
+        2. Under **App Content**, declare the use of the **Advertising ID**.
+        3. Provide all required information accurately.
+
+        Failure to declare this can prevent ads from loading during testing or after release.
+
+:::tip[Additional Configuration Tips]
+
+- **Connectivity:** Ensure stable internet connectivity on the device.
+- **Ad Unit Configuration:** Double-check that your **Ad Unit IDs** are correct in FlutterFlow.
+- **APP-ADS.TXT:**  
+  While optional, setting up an **app-ads.txt** file can improve ad quality and protect against unauthorized ad traffic. **[Learn more](https://support.google.com/admob/answer/10299703)**.
+:::
+
+:::info[Ad Approval Process]
+Even after moving your app to production and receiving **AdMob** approval, it can take a few days for live ads to start appearing fully. This delay is normal.
+:::
+
+If you continue to experience issues, please contact **FlutterFlow Support** at [[email protected]](mailto:[email protected]).

docs/troubleshooting/google-play-store-deployment-issues/failed-step-publishing/declare_advertising_id_android_13_play_console.md

@@ -0,0 +1,51 @@
+---
+keywords: ['api', 'android', 'error']
+slug: /declare-advertising-id-android-13-play-console
+title: Declare Advertising ID for Android 13+ in Play Console
+---
+# Declare Advertising ID for Android 13+ in Play Console
+
+:::info[Prerequisites]
+- You are submitting your app to Google Play targeting Android 13 (API 33) or above.
+:::
+
+When uploading your app to Google Play, you may encounter this error:
+
+```js
+Google Play failed to upload artefacts. Your app targets Android 13 (API 33) or above. You must declare the use of advertising ID in Play Console.: {    "error": {        "code": 400,        "message": "Your app targets Android 13 (API 33) or above. You must declare the use of advertising ID in Play Console.",        "status": "INVALID_ARGUMENT"    }}
+```
+
+Google Play now requires developers targeting Android 13 (API 33) or above to explicitly declare if their app uses the **Advertising ID**.
+
+You may see this error if:
+
+    - You didn't complete the advertising ID declaration in the Play Console.
+    - Your app configuration suggests ad usage but you have not declared it.
+    - Your declaration is incomplete or missing required details.
+
+Follow the steps below to fix this error:
+
+Step 1 — Open App Content Section in Play Console
+
+    - Log into your **Google Play Console**.
+    - Navigate to your app's **App Content** section.
+
+    ![](../../assets/20250430121230522324.png)
+
+Step 2 — Declare Advertising ID Usage
+
+    - If your app **does not contain ads**, select **No** under the "Advertising ID" section.
+
+    ![](../../assets/20250430121230823138.png)
+
+    - If your app **contains ads**, select **Yes** and provide the necessary details about how ads are used.
+
+    This Declaration is important because Google Play uses this information to:
+
+        - Inform users about your app’s data collection practices.
+        - Ensure compliance with privacy policies.
+        - Prevent build upload failures.
+
+
+If the issue persists after following these steps, please contact FlutterFlow Support via Chat or email at [[email protected]](mailto:[email protected]).
+

docs/troubleshooting/google-play-store-deployment-issues/failed-step-publishing/google_play_draft_release_error.md

@@ -0,0 +1,38 @@
+---
+keywords: ['deployment', 'error', 'releases']
+slug: /google-play-draft-release-error
+title: Google Play Draft Release Error
+---
+# Google Play Draft Release Error
+
+```js
+Google Play failed to upload artifacts. Only releases with status draft may be created on draft app.: {    "error": {        "code": 400,        "message": "Only releases with status draft may be created on draft app.",        "status": "INVALID_ARGUMENT"    } }
+```
+
+The error above indicates that Google Play only allows you to create a **Draft Release** when your app is still marked as a draft in your Google Play Console. You likely have missing or incomplete app information in Google Play preventing full release submission.
+
+One of the most common causes of a publishing error when deploying to the Google Play Store is when you haven't filled out all the necessary information in the Play Store before deploying the application.
+
+Follow these steps to fix the issue:
+
+:::note
+Make sure that you fill out all the information in the Play Store including the store listing information and the setup information.
+:::
+
+- **Step 1**: 
+
+    On the projects dashboard, navigate to the **settings and integrations** section.​
+
+    ![](../../assets/20250430121320431269.png)
+
+- **Step 2**:
+
+    Navigate to the **Mobile Deployment** section.​
+
+    ![](../../assets/20250430121320759595.png)
+
+- **Step 3**:
+
+    Under the Google Play Store Deployment section, toggle on **submit as draft**.
+
+    ![](../../assets/20250430121321051936.png)