FlutterFlow · mrdavidorok · Jun 6, 2025
diff --git a/docs/troubleshooting/assets/20250430121230522324.png b/docs/troubleshooting/assets/20250430121230522324.png
diff --git a/docs/troubleshooting/assets/20250430121230823138.png b/docs/troubleshooting/assets/20250430121230823138.png
diff --git a/docs/troubleshooting/assets/20250430121320431269.png b/docs/troubleshooting/assets/20250430121320431269.png
diff --git a/docs/troubleshooting/assets/20250430121320759595.png b/docs/troubleshooting/assets/20250430121320759595.png
diff --git a/docs/troubleshooting/assets/20250430121321051936.png b/docs/troubleshooting/assets/20250430121321051936.png
diff --git a/docs/troubleshooting/assets/20250430121327988277.gif b/docs/troubleshooting/assets/20250430121327988277.gif
diff --git a/docs/troubleshooting/assets/20250430121330484821.png b/docs/troubleshooting/assets/20250430121330484821.png
diff --git a/docs/troubleshooting/assets/20250430121330727549.png b/docs/troubleshooting/assets/20250430121330727549.png
diff --git a/docs/troubleshooting/assets/20250430121331069027.png b/docs/troubleshooting/assets/20250430121331069027.png
diff --git a/docs/troubleshooting/assets/20250430121331806679.png b/docs/troubleshooting/assets/20250430121331806679.png
diff --git a/docs/troubleshooting/assets/20250430121332062568.png b/docs/troubleshooting/assets/20250430121332062568.png
diff --git a/docs/troubleshooting/assets/20250430121513060363.png b/docs/troubleshooting/assets/20250430121513060363.png
diff --git a/docs/troubleshooting/assets/20250430121513225263.png b/docs/troubleshooting/assets/20250430121513225263.png
diff --git a/docs/troubleshooting/google-play-store-deployment-issues/_category_.json b/docs/troubleshooting/google-play-store-deployment-issues/_category_.json
@@ -0,0 +1,3 @@
+{
+  "label": "Google Play Store Deployment Issues"
+}
diff --git a/...ng/google-play-store-deployment-issues/failed-step-build-aab-with-flutter/_category_.json b/...ng/google-play-store-deployment-issues/failed-step-build-aab-with-flutter/_category_.json
@@ -0,0 +1,3 @@
+{
+  "label": "Build AAB With Flutter"
+}
diff --git a/...ter/you_uploaded_an_apk_or_android_app_bundle_that_was_signed_in_debug_mode..md b/...ter/you_uploaded_an_apk_or_android_app_bundle_that_was_signed_in_debug_mode..md
@@ -0,0 +1,36 @@
+---
+keywords: ['debug', 'android', 'release']
+slug: /you-uploaded-an-apk-or-android-app-bundle-that-was-signed-in-debug-mode
+title: You uploaded an APK or Android App Bundle that was signed in debug mode.
+---
+# You uploaded an APK or Android App Bundle that was signed in debug mode.
+
+
+Unsure about the type of error in your project? Refer to this article to learn how to identify Codemagic errors.
+
+## What does this error mean?
+
+You need to sign your APK or Android App Bundle in **release mode** instead of debug mode.
+
+## Full error message
+
+```
+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
+```
+
+## How to resolve this issue
+
+You'll need to modify your android/app level build.gradle file and replace `debug` with `release`. 
+
+Follow the steps below: 
+
+- 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)
+
+## The issue was not resolved
+
+If this does not resolve the issue, contact FlutterFlow Support at support@flutterflow.io
diff --git a/...ting/google-play-store-deployment-issues/failed-step-generate-launch-icon/_category_.json b/...ting/google-play-store-deployment-issues/failed-step-generate-launch-icon/_category_.json
@@ -0,0 +1,3 @@
+{
+  "label": "Generate Launch Icon"
+}
diff --git a/...iled_step_generate_launch_icon_could_not_find_package_flutter_launcher_icons.md b/...iled_step_generate_launch_icon_could_not_find_package_flutter_launcher_icons.md
@@ -0,0 +1,36 @@
+---
+keywords: ['error', 'package', 'icon']
+slug: /failed-step-generate-launch-icon-could-not-find-package-flutter-launcher-icons
+title: 'Failed Step: Generate Launch Icon Could not find package "flutter_launcher_icons"'
+---
+
+Full Error Message
+```
+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. 
+```
+
+**What does this error mean?**
+The flutter icon launcher dependency was not recognized in the source code. **How do I resolve this issue?**
+
+When deploying directly from FlutterFlow. 
+
+![](../../assets/20250430121327988277.gif)
+Navigate to the **settings and integrations &gt; App Assets. **If the **Splash Screen** and **Launcher Icon** are already set, clear them and re-upload once more. 2. Deploying from GitHub Requirements
+
+Package flutter_launcher_icons 0.10.0 or higher
+
+android.png (App icon for Android)
+
+ios.png (App icon for iOS)1. Add the flutter_launcher_icon package to the pubspec.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"  
+```
+
+Whereby, 1. `dev_dependencies: flutter_launcher_icons: “0.10.0”`: Refers to the package version that will be installed2. `image_path_ios`: This is the location where the application launcher image for ios is found.
+3. `image_path_android`: Just like image_path_ios, image_path_android refers to the location where the app launcher image for android is stored.
+2. Build  and run the applicationTo run and build the application, run the following source code in your integrated development environment 
+```
+flutter pub getflutter pub run flutter_launcher_icons:mainflutter run
+```
+
+This was not resolved. If the issue still persists, contact support@flutterflow.io for further assistance.
diff --git a/...ncher_icon_is_not_showing_up_even_though_I_had_added_it_in_project_settings..md b/...ncher_icon_is_not_showing_up_even_though_I_had_added_it_in_project_settings..md
@@ -0,0 +1,32 @@
+---
+keywords: ["icon", "added", "launcher"]
+slug: /my-app-launcher-icon-is-not-showing-up-even-though-i-had-added-it-in-project-settings
+title: My app launcher icon is not showing up even though I had added it in project settings.
+---
+
+# My app launcher icon is not showing up even though I had added it in project settings
+
+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.
+
+---
+
+**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.
+
+For more details, see the [FlutterFlow help article]({{url}}).
diff --git a/...ting/google-play-store-deployment-issues/failed-step-get-flutter-packages/_category_.json b/...ting/google-play-store-deployment-issues/failed-step-get-flutter-packages/_category_.json
@@ -0,0 +1,3 @@
+{
+  "label": "Get Flutter Packages"
+}
diff --git a/...ecause_project_name_depends_on_flutter_test_from_sdk_version_solving_failed..md b/...ecause_project_name_depends_on_flutter_test_from_sdk_version_solving_failed..md
@@ -0,0 +1,27 @@
+---
+keywords: ['error', 'version', 'failed']
+slug: /because-project-name-depends-on-flutter-test-from-sdk-version-solving-failed
+title: Because [project name] depends on flutter_test from sdk, version solving failed.
+---
+# Because [project name] depends on flutter_test from sdk, version solving failed.
+
+Tip: Not sure which type of error your project has? Check out this article on how to identify your Codemagic error.
+
+**What does this error mean?**
+This issue happens when there are packages in your project with incompatible versions. 
+
+**Full error message**
+```
+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
+```
+
+**How to resolve this 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 support@flutterflow.io.
+
diff --git a/.../failed-step-get-flutter-packages/i_get_this_error_error_running_pod_install.md b/.../failed-step-get-flutter-packages/i_get_this_error_error_running_pod_install.md
@@ -0,0 +1,32 @@
+---
+keywords: ['error', 'running', 'install']
+slug: /i-get-this-error-error-running-pod-install
+title: 'I get this error: Error running pod install'
+---
+
+# I get this error: 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.
+
+## How to Fix
+
+- 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)
+
+## 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
+  ```
+
+If you still encounter problems, refer to the [Flutter documentation](https://docs.flutter.dev/) or reach out to support.
diff --git a/...roubleshooting/google-play-store-deployment-issues/failed-step-publishing/_category_.json b/...roubleshooting/google-play-store-deployment-issues/failed-step-publishing/_category_.json
@@ -0,0 +1,3 @@
+{
+  "label": "Publishing"
+}
diff --git a/...step-publishing/admob_ad_display_issues_in_open_testing_on_google_play_store.md b/...step-publishing/admob_ad_display_issues_in_open_testing_on_google_play_store.md
@@ -0,0 +1,41 @@
+---
+keywords: ['testing', 'configuration', 'display']
+slug: /admob-ad-display-issues-in-open-testing-on-google-play-store
+title: AdMob Ad Display Issues in Open Testing on Google Play Store
+---
+# AdMob Ad Display Issues in Open Testing on Google Play Store
+
+If you’re experiencing issues with AdMob ads not displaying during open testing on the Google Play Store, you’re not alone. A common concern is that ads initially show but then suddently stops, and starts displaying only as "**Ad Loading**."
+
+The primary reason for ads not displaying during open testing is often the use of live ads instead of test ads, as well as proper configuration of AdMob and advertising IDs. 
+
+Don't forget about the **Ad Approval Process**. After moving your app to production and receiving approval from AdMob, it can take a few days for ads to start appearing in your app. This delay is normal and should be expected.
+
+## Steps to Ensure Ad Functionality:
+
+Here are a few steps to take to make sure your ads are functioning properly in your app.
+
+### 1. Use Test Ads During App Testing
+
+When testing your app, always use test ads — this will help to avoid issues. Live ads are designed to show only when the app is in production.
+
+### 2. Check AdMob Settings
+
+Verify that your AdMob settings reflect the correct release status of your app. If your app is marked as not released in AdMob, your live ads will not display.
+
+### 3. Advertising ID Declaration
+
+For apps targeting Android 13 (API 33) or above, you must declare the use of the advertising ID in the Google Play Console. Ensure all information is complete and accurate to prevent ads from not loading.
+
+## Additional Tips
+
+### APP-ADS.TXT
+
+While optional, setting up the APP-ADS.TXT file can improve ad quality and security.
+
+### Connectivity and Ad Unit Configuration: 
+
+Ensure there are no issues with internet connectivity or ad unit configurations.
+
+
+For additional guidance, visit FlutterFlow Documentation and the FlutterFlow Community.
diff --git a/...ed-step-publishing/google_play_failed_to_upload_artefacts_package_not_found..md b/...ed-step-publishing/google_play_failed_to_upload_artefacts_package_not_found..md
@@ -0,0 +1,49 @@
+---
+keywords: ['firebase', 'error', 'package']
+slug: /google-play-failed-to-upload-artefacts-package-not-found
+title: Google Play Failed to Upload Artefacts. Package not Found.
+---
+# Google Play Failed to Upload Artefacts. Package not Found
+
+Not sure what kind of error your project is encountering? Review this article to learn how to identify Codemagic errors..
+
+## What does this error mean?
+
+This issue can result from two scenarios: 
+- When it is the first time you are deploying your application to the Play Store, or 
+- When you update your app's package name but don't update the config files.
+
+## Full Error Message
+
+```
+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"    }}
+```
+
+## How to resolve this issue?
+
+### First time project deployment
+
+To resolve this issue for first time project deployme to play sore, you will need to download the AAB that was generated and manually upload it to paystore. This is required for teh initial first time deployment, after that the subsiquest deployment should go on without any disruption or the same error being through 
+
+- Click on the button marked "AAB" to download the build.
+
+- Open your Play Store account under the registered project, and upload it as a release depending on the track you are uploading the build to.
+
+    ![](../../assets/20250430121330484821.png)
+
+### Package Id update 
+To resolve this issue, please follow the steps below:
+
+- You'll need to Regenerate the config files from FlutterFlow. To do this, open your app in **FlutterFlow** and then click on **Settings** **&gt;** **Firebase**.
+    ![](../../assets/20250430121330727549.png)
+
+- Here, Click on the **Regenerate Config Files **button, Enter the new package name and then Click on **Generate File.**
+    ![](../../assets/20250430121331069027.png)
+
+This issue should now be resolved. You can now re-deploy to confirm that the issue has been fixed.
+
+## Issue was not resolved after following the given steps
+
+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 Chat or Email at support@flutterflow.io.
+
+
diff --git a/...deployment-issues/failed-step-publishing/google_play_store_deployment_issues.md b/...deployment-issues/failed-step-publishing/google_play_store_deployment_issues.md
@@ -0,0 +1,27 @@
+---
+keywords: ['deployment', 'debug', 'android']
+slug: /google-play-store-deployment-issues
+title: Google Play Store Deployment Issues
+---
+# Google Play Store Deployment Issues
+
+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
+
+You'll need to modify your android/app-level build.gradle file and replace `debug` with `release`. You'll need to replace the debug keyword with the release.
+
+Here are the instructions on how to do this:
+
+- Find the debug keyword under buildTypes in android/app/builld.gradle in your project folder.
+
+![](../../assets/20250430121513060363.png)
+
+- Replace the debug keyword with release and then save the file.
+
+![](../../assets/20250430121513225263.png)
+
+
+
+Please make sure that you fill out all the information in the play store including the store listing information and the setup information.
+
+
+
diff --git a/...-step-publishing/only_releases_with_status_draft_may_be_created_on_draft_app.md b/...-step-publishing/only_releases_with_status_draft_may_be_created_on_draft_app.md
@@ -0,0 +1,42 @@
+---
+keywords: ['deployment', 'error', 'releases']
+slug: /only-releases-with-status-draft-may-be-created-on-draft-app
+title: Only Releases with Status Draft may be Created on Draft App
+---
+# Only Releases with Status Draft may be Created on Draft App
+
+Not sure which type of Codemagic error you're running into? 
+Check out this article on how to identify your Codemagic error.
+
+
+## Full Error Message
+
+```
+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"    } }
+```
+
+## Most Common Error
+
+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.
+
+### How To Resolve This Issue
+
+Please make sure that you fill out all the information in the Play Store including the store listing information and the setup information. Then, please follow the steps outlined below:
+
+#### 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)
diff --git a/...station_api_is_being_discontinued_and_replaced_by_the_new_play_integrity_api.md b/...station_api_is_being_discontinued_and_replaced_by_the_new_play_integrity_api.md
@@ -0,0 +1,37 @@
+---
+keywords: ['api', 'attestation', 'being']
+slug: /the-safety-attestation-api-is-being-discontinued-and-replaced-by-the-new-play-integrity-api
+title: The Safety Attestation API is being discontinued and replaced by the new Play
+  Integrity API
+---
+# The Safety Attestation API is Being Discontinued and Replaced by the new Play Integrity API
+
+## Full Error Message
+
+```
+The SafetyNet Attestation API is being discontinued and replaced by the new Play Integrity API. Begin migration as soon as possible to avoid user disruption. The Play Integrity API includes all the integrity signals that SafetyNet Attestation offers and more, like Google Play licensing and better error messaging. Learn more and start migrating at http://developer.android/training/safetynet/depreciation-time
+```
+
+## What is the SafetyNet Attestation API?
+
+The SafetyNet Attestation API is a Google API that enables Android developers to assess the integrity of their devices at runtime. It enables developers to gain insight into the security hazards on their devices and take any necessary action their applications need to ensure they are not susceptible to attack.
+
+The API works by submitting a request to Google's servers, which will respond with a signed "attestation token" that contains information about the device, such as its API level, bootloader state, security patch level, and its Google Play services version.
+
+By analyzing this data, you can make decisions about your application's security, such as rejecting requests from devices that are rooted or out-of-date. This provides an additional layer of protection against malicious or security-hazardous devices.
+
+In order to use the SafetyNet Attestation API, developers need to register their Android application with Google. Once registered, SafetyNet will be able to provide the attestation token when requested.
+
+You can learn more about [SafetyNet Attestation API Documentation](https://developer.android.com/training/safetynet/attestation) at the Google Developer website.
+
+## Why should I migrate? 
+
+In order to ensure the best user experience and create a more secure platform, it is important that you migrate to the new Play Integrity API as soon as possible. The Play Integrity API provides better security, a larger range of user data, and improved error messaging. 
+
+## How can I start migrating? 
+
+Migrating from the SafetyNet Attestation API to the Play Integrity API is easy. Just visit http://developer.android/training/safetynet/depreciation-time to learn more and start migrating. 
+
+## What if I run into an issue? 
+
+If you encounter any issues during the migration process, please contact our support team and they will be happy to assist you.