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

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

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

docs/troubleshooting/google-play-store-deployment/admob_ads_not_displaying_in_google_play_testing.md

@@ -0,0 +1,70 @@
+---
+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
+
+If your AdMob ads are not showing during **Open Testing** via the Google Play Store, the issue is often tied to AdMob configuration, app permissions, or settings in the Google Play Console. Follow the steps below to ensure ads display correctly.
+
+:::info[Prerequisites]
+- An active **AdMob** account is set up.
+- Your FlutterFlow project is linked to **AdMob**.
+- The app is uploaded to **Google Play Console** under an Open Testing track.
+:::
+
+- **Use Test Ads During Development**
+
+    Always use test ads during development to avoid policy violations or ad-serving issues:
+        - Refer to the **[Google AdMob Test Ads](https://developers.google.com/admob/android/test-ads)** guide for appropriate test ad unit IDs.
+        - Live ads should be used only after your app is published to production and approved.
+
+- **Verify AdMob Account Setup**
+
+    1. Go to the **AdMob Console**.
+    2. Confirm that your app is registered and linked to your Google Play listing.
+    3. Ensure the app’s release status in AdMob matches its status in the **Google Play Console**.
+
+        :::note
+        If your app is listed as `not released` in AdMob, live ads may not load during testing.
+        :::
+
+- **Declare Use of Advertising ID**
+
+    Apps targeting **Android 13 (API 33)** or above must declare use of the **Advertising ID**:
+
+    1. Open the **Google Play Console**.
+    2. Go to **Policy > App Content**.
+    3. Select **Advertising ID** and complete the required form.
+
+        :::warning
+        Failing to declare the Advertising ID may result in ads not showing during testing or after release.
+        :::
+
+- **Confirm Ad Unit Configuration in FlutterFlow**
+
+    1. Open your project in **FlutterFlow**.
+    2. Navigate to **Settings > AdMob Integration**.
+    3. Confirm that the correct **Ad Unit IDs** are used.
+    4. Ensure Ad widgets are connected to the appropriate ad units.
+
+- **Test in the Correct Environment**
+
+    - Use a physical device instead of an emulator when possible.
+    - Ensure the device has a strong internet connection.
+    - Avoid using VPNs or battery optimization tools that may interfere with ad delivery.
+
+- **Add app-ads.txt (Optional)**
+
+    Setting up an `app-ads.txt` file is optional but recommended for better ad quality:
+        - Follow the **[official guide](https://support.google.com/admob/answer/9363762?hl=en&ref_topic=9675856&sjid=8136071085841576181-EU)** to set it up.
+
+- **Wait for Ad Approval**
+
+    Even after the app is released:
+
+    - Live ads may take several days to appear due to the review process and inventory matching.
+    - This delay is expected.
+
+If ads still aren’t appearing, contact FlutterFlow Support at [[email protected]](mailto:[email protected])

docs/troubleshooting/google-play-store-deployment/declare_advertising_id_android_13_play_console.md

@@ -0,0 +1,61 @@
+---
+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
+
+If your app targets Android 13 (API 33) or higher, Google Play requires that you declare whether your app uses the **Advertising ID**. Failing to do so will result in an upload error when submitting artifacts to the Play Console.
+
+:::info[Prerequisites]
+- Your app targets Android 13 (API 33) or above.
+- The app is being submitted via the **Google Play Console**.
+:::
+
+When uploading your app to Google Play, you may encounter this error:
+
+    ```js
+    {
+    "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"
+    }
+    }
+    ```
+    This error occurs when the required declaration for the Advertising ID is missing, incomplete, or inconsistent with your app configuration.
+
+    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:
+
+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)
+
+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/error_running_pod_install.md

@@ -0,0 +1,45 @@
+---
+keywords: ['error', 'running', 'install']
+slug: /error-running-pod-install
+title: Error Running Pod Install
+---
+
+# Error Running Pod Install
+
+This article addresses the common **Error Running Pod Install** issue, which typically occurs due to misconfiguration of Flutter or CocoaPods on macOS devices.
+
+:::info[Prerequisites]
+- Flutter is installed on your development machine.
+- You are working on a macOS device.
+- Basic familiarity with terminal commands.
+:::
+
+## Steps to Fix Error Running Pod Install:
+
+1. Verify Flutter is set up correctly by following the official guide: **[Flutter - Get Started: Install on macOS](https://docs.flutter.dev/get-started/install/macos)**.
+
+2. For troubleshooting specific to macOS, consult this guide: **[Troubleshooting Flutter on macOS](https://docs.flutter.dev/get-started/install/macos/mobile-ios#install-cocoapods)**.
+
+3. Run `flutter doctor` in the terminal to check for missing dependencies or configuration issues.
+
+4. Ensure CocoaPods is installed and up to date by running the following commands:
+
+   ```bash
+   sudo gem install cocoapods
+   pod repo update
+
+5. If the problem persists, try deleting the CocoaPods cache and reinstalling:
+
+  ```bash
+  flutter clean
+  ```
+  ```bash
+  flutter pub get
+  ```
+  ```bash
+  cd ios
+  ```
+  ```bash
+  pod install
+  ```
+  Deleting the `ios/Pods` directory and `ios/Podfile.lock` file before running `pod install` can help resolve lingering CocoaPods issues.

docs/troubleshooting/google-play-store-deployment/fix_launcher_icons_package_error.md

@@ -0,0 +1,75 @@
+---
+keywords: ['error', 'package', 'icon']
+slug: /fix-launcher-icons-package-error
+title: Fix Flutter Launcher Icons Package Error
+---
+
+# Fix Flutter Launcher Icons Package Error
+
+This article describes how to resolve the **[flutter_launcher_icons package](https://pub.dev/packages/flutter_launcher_icons)** error that may occur during app build or deployment.
+
+:::info[Prerequisites]
+- Access to your FlutterFlow project.
+- Ability to open and edit the `pubspec.yaml` file.
+- Familiarity with your build environment (FlutterFlow, GitHub, or IDE).
+:::
+
+**Understanding the Error:**
+
+During the build process, you might see the following error message:
+
+```text
+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 indicates that the **flutter_launcher_icons** package is missing or not configured correctly.
+
+Follow the steps below to fix the error:
+
+1. **Clear and Reset App Assets in FlutterFlow:**
+    - Navigate to **Settings and Integrations** > **App Assets** inside FlutterFlow.
+    - If the **Splash Screen** and **Launcher Icon** are set:
+        - Clear both assets.
+        - Re-upload the launcher icons.
+
+        ![](../assets/20250430121327988277.gif)
+
+2. **`Add flutter_launcher_icons` Package in GitHub Deployment**
+    If you are deploying via GitHub and encounter this error, add the package to your `pubspec.yaml` file:
+
+        - Open your `pubspec.yaml` file.
+        - Add the following under `dev_dependencies`:
+
+            ```js
+            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"
+            ```
+            - **flutter_launcher_icons*: "^0.10.0" specifies the package version.
+            - `image_path_ios` and `image_path_android` specify the paths to your launcher icon images.
+            - Ensure the image files exist at the specified paths.
+
+3. **Run the following commands in your terminal or IDE:**
+
+    ```bash
+    flutter pub get
+    ```
+    ```bash
+    flutter pub run flutter_launcher_icons:main
+    ```
+    ```bash
+    flutter run
+    ```
+    `flutter pub get` fetches packages.
+
+    `flutter pub run flutter_launcher_icons:main` generates launcher icons.
+
+    `flutter run` builds and runs the app.
+
+If the issue persists after following these steps, contact FlutterFlow Support at [email protected].
+

docs/troubleshooting/google-play-store-deployment/google_play_draft_release_error.md

@@ -0,0 +1,64 @@
+---
+keywords: ['deployment', 'error', 'releases']
+slug: /google-play-draft-release-error
+title: Google Play Draft Release Error
+---
+
+# Google Play Draft Release Error
+
+When uploading an app to Google Play, you may encounter the following error:
+
+```js
+{
+  "error": {
+    "code": 400,
+    "message": "Only releases with status draft may be created on draft app.",
+    "status": "INVALID_ARGUMENT"
+  }
+}
+```
+
+This error occurs because Google Play only allows creating a Draft Release if your app is still marked as a draft in the Google Play Console. Typically, this means some required app information in the Play Console has not been completed, preventing full release submission.
+
+:::info[Prerequisites]
+- Your app is registered in the Google Play Console.
+- Basic app details such as store listing and setup information are ready to be filled.
+:::
+
+This error 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.
+
+
+Follow these steps to fix the issue:
+
+1. Complete All Required Information in Google Play Console
+
+    - Log in to your **Google Play Console**.
+    - Complete all mandatory sections under:
+        - **App Content**
+        - **Store Listing**
+        - **Pricing & Distribution**
+        - **Target Audience & Content Rating**
+
+        Google Play requires all required information to be filled out before allowing full production releases.
+
+2. **Enable "Submit As Draft" in FlutterFlow**
+
+    After completing your app information, proceed as follows:
+
+        - **Open Settings and Integrations**: From your FlutterFlow project dashboard, navigate to **Settings > Integrations**.
+
+            ![](../assets/20250430121320431269.png)
+
+        - **Navigate to Mobile Deployment**: Select **Mobile Deployment**.
+
+            ![](../assets/20250430121320759595.png)
+
+        - **Enable Submit As Draft**: Under **Google Play Store Deployment**, toggle on **Submit as Draft**.
+
+            ![](../assets/20250430121321051936.png)
+
+            This allows you to submit your release as a draft until all Google Play requirements are fully satisfied.
+
+
+If you’ve followed all steps and still encounter the issue, contact **FlutterFlow Support** via Chat or email at [[email protected]](mailto:[email protected]) for additional assistance.
+

docs/troubleshooting/google-play-store-deployment/google_play_failed_to_upload_artefacts_package.md

@@ -0,0 +1,61 @@
+---
+keywords: ['firebase', 'error', 'package']
+slug: /google-play-failed-to-upload-artefacts
+title: Google Play Failed to Upload Artefacts
+---
+
+# Google Play Failed to Upload Artefacts
+
+:::info[Prerequisites]
+- Ensure your app’s `Package Name` in FlutterFlow matches the package name in Google Play Console.
+- Firebase is configured in your project settings.
+- Your Google Play Console account is active and accessible.
+:::
+
+When uploading your app to Google Play, you may encounter the following error:
+
+```js
+Google Play failed to upload artefacts. Package not found: com.flutterflow.appname.: {
+  "error": {
+    "code": 404,
+    "message": "Package not found: com.flutterflow.appname.",
+    "status": "NOT_FOUND"
+  }
+}
+```
+
+This error usually occurs in two scenarios:
+- Deploying the app to Google Play for the first time.
+- Changing the app’s `Package Name` in FlutterFlow without regenerating the Firebase configuration files.
+
+**First Time Deployment to Google Play**
+
+Follow these steps to upload your app for the first time:
+
+    1. Generate your build in FlutterFlow and click the `AAB` button to download the build artifact.
+    2. Log in to your **[Google Play Console](https://play.google.com/console)**.
+    3. Navigate to your app project and upload the **AAB** file as a new release in the appropriate track (Internal, Closed, Open, or Production).
+    4. After this initial upload, future deployments should proceed without this error.
+
+        ![](../assets/20250430121330484821.png)
+
+**Updating Package Name and Regenerating Config Files**
+
+If you have updated your app’s `Package Name` in FlutterFlow, follow these steps:
+    1. Open your project in FlutterFlow.
+    2. Navigate to **Settings** > **Firebase**.
+    3. Click **Regenerate Config Files**.
+
+        ![](../assets/20250430121330727549.png)
+
+    4. Enter the new `Package Name` and click Generate File to download the updated configuration files.
+
+        ![](../assets/20250430121331069027.png)
+
+    5. Rebuild and redeploy your app to confirm the error is resolved.
+
+If the error persists after completing these steps:
+    - Verify the `Package Name` matches exactly between FlutterFlow and Google Play Console.
+    - Confirm that Firebase configuration files have been updated correctly.
+    - Contact FlutterFlow Support via Chat or email at [email protected].
+