Description
Can we access your project?
- I give permission for members of the FlutterFlow team to access and test my project for the sole purpose of investigating this issue.
Current Behavior
When I want to deploy my build on google play, I get this error message:
<style> body { color:#C8C8C8; overflow-x: hidden; padding-top: 0px; padding-right: 5px; padding-bottom: 5px; padding-left: 5px; font-family: monaco; } h4 { margin-bottom: 4px; font-weight: bold; color: #DF3F3F; } </style>Failed Step: Build AAB with Flutter
Package google_api_headers:linux references google_api_headers:linux as the default plugin, but it does not provide an inline implementation.
Ask the maintainers of google_api_headers to either avoid referencing a default implementation via platforms: linux: default_package: google_api_headers
or add an inline implementation to google_api_headers via platforms: linux:
pluginClass
or dartPluginClass
.
Package google_api_headers:macos references google_api_headers:macos as the default plugin, but it does not provide an inline implementation.
Ask the maintainers of google_api_headers to either avoid referencing a default implementation via platforms: macos: default_package: google_api_headers
or add an inline implementation to google_api_headers via platforms: macos:
pluginClass
or dartPluginClass
.
Package google_api_headers:windows references google_api_headers:windows as the default plugin, but it does not provide an inline implementation.
Ask the maintainers of google_api_headers to either avoid referencing a default implementation via platforms: windows: default_package: google_api_headers
or add an inline implementation to google_api_headers via platforms: windows:
pluginClass
or dartPluginClass
.
Package google_api_headers:ios references google_api_headers:ios as the default plugin, but it does not provide an inline implementation.
Ask the maintainers of google_api_headers to either avoid referencing a default implementation via platforms: ios: default_package: google_api_headers
or add an inline implementation to google_api_headers via platforms: ios:
pluginClass
or dartPluginClass
.
Package google_api_headers:linux references google_api_headers:linux as the default plugin, but it does not provide an inline implementation.
Ask the maintainers of google_api_headers to either avoid referencing a default implementation via platforms: linux: default_package: google_api_headers
or add an inline implementation to google_api_headers via platforms: linux:
pluginClass
or dartPluginClass
.
Package google_api_headers:macos references google_api_headers:macos as the default plugin, but it does not provide an inline implementation.
Ask the maintainers of google_api_headers to either avoid referencing a default implementation via platforms: macos: default_package: google_api_headers
or add an inline implementation to google_api_headers via platforms: macos:
pluginClass
or dartPluginClass
.
Package google_api_headers:windows references google_api_headers:windows as the default plugin, but it does not provide an inline implementation.
Ask the maintainers of google_api_headers to either avoid referencing a default implementation via platforms: windows: default_package: google_api_headers
or add an inline implementation to google_api_headers via platforms: windows:
pluginClass
or dartPluginClass
.
Package google_api_headers:ios references google_api_headers:ios as the default plugin, but it does not provide an inline implementation.
Ask the maintainers of google_api_headers to either avoid referencing a default implementation via platforms: ios: default_package: google_api_headers
or add an inline implementation to google_api_headers via platforms: ios:
pluginClass
or dartPluginClass
.
Package google_api_headers:linux references google_api_headers:linux as the default plugin, but it does not provide an inline implementation.
Ask the maintainers of google_api_headers to either avoid referencing a default implementation via platforms: linux: default_package: google_api_headers
or add an inline implementation to google_api_headers via platforms: linux:
pluginClass
or dartPluginClass
.
Package google_api_headers:macos references google_api_headers:macos as the default plugin, but it does not provide an inline implementation.
Ask the maintainers of google_api_headers to either avoid referencing a default implementation via platforms: macos: default_package: google_api_headers
or add an inline implementation to google_api_headers via platforms: macos:
pluginClass
or dartPluginClass
.
Package google_api_headers:windows references google_api_headers:windows as the default plugin, but it does not provide an inline implementation.
Ask the maintainers of google_api_headers to either avoid referencing a default implementation via platforms: windows: default_package: google_api_headers
or add an inline implementation to google_api_headers via platforms: windows:
pluginClass
or dartPluginClass
.
Upgrading build.gradle
Running Gradle task 'bundleRelease'...
Checking the license for package Android SDK Build-Tools 33.0.1 in /usr/local/share/android-sdk/licenses
License for package Android SDK Build-Tools 33.0.1 accepted.
Preparing "Install Android SDK Build-Tools 33.0.1 v.33.0.1".
"Install Android SDK Build-Tools 33.0.1 v.33.0.1" ready.
Installing Android SDK Build-Tools 33.0.1 in /usr/local/share/android-sdk/build-tools/33.0.1
"Install Android SDK Build-Tools 33.0.1 v.33.0.1" complete.
"Install Android SDK Build-Tools 33.0.1 v.33.0.1" finished.
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
Package google_api_headers:ios references google_api_headers:ios as the default plugin, but it does not provide an inline implementation.
Ask the maintainers of google_api_headers to either avoid referencing a default implementation via platforms: ios: default_package: google_api_headers
or add an inline implementation to google_api_headers via platforms: ios:
pluginClass
or dartPluginClass
.
Package google_api_headers:linux references google_api_headers:linux as the default plugin, but it does not provide an inline implementation.
Ask the maintainers of google_api_headers to either avoid referencing a default implementation via platforms: linux: default_package: google_api_headers
or add an inline implementation to google_api_headers via platforms: linux:
pluginClass
or dartPluginClass
.
Package google_api_headers:macos references google_api_headers:macos as the default plugin, but it does not provide an inline implementation.
Ask the maintainers of google_api_headers to either avoid referencing a default implementation via platforms: macos: default_package: google_api_headers
or add an inline implementation to google_api_headers via platforms: macos:
pluginClass
or dartPluginClass
.
Package google_api_headers:windows references google_api_headers:windows as the default plugin, but it does not provide an inline implementation.
Ask the maintainers of google_api_headers to either avoid referencing a default implementation via platforms: windows: default_package: google_api_headers
or add an inline implementation to google_api_headers via platforms: windows:
pluginClass
or dartPluginClass
.
Font asset "CupertinoIcons.ttf" was tree-shaken, reducing it from 257628 to 1832 bytes (99.3% reduction). Tree-shaking can be disabled by providing the --no-tree-shake-icons flag when building your app.
Font asset "fa-brands-400.ttf" was tree-shaken, reducing it from 207972 to 1348 bytes (99.4% reduction). Tree-shaking can be disabled by providing the --no-tree-shake-icons flag when building your app.
Font asset "fa-solid-900.ttf" was tree-shaken, reducing it from 419720 to 1816 bytes (99.6% reduction). Tree-shaking can be disabled by providing the --no-tree-shake-icons flag when building your app.
Font asset "MaterialIcons-Regular.otf" was tree-shaken, reducing it from 1645184 to 17480 bytes (98.9% reduction). Tree-shaking can be disabled by providing the --no-tree-shake-icons flag when building your app.
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
FAILURE: Build completed with 2 failures.
1: Task failed with an exception.
-
What went wrong:
Execution failed for task ':app:processReleaseResources'.
> A failure occurred while executing com.android.build.gradle.internal.res.LinkApplicationAndroidResourcesTask$TaskAction
> Android resource linking failed
/home/builder/clone/build/app/intermediates/packaged_manifests/release/AndroidManifest.xml:74: error: resource string/facebook_client_token (aka app.kontnu.com:string/facebook_client_token) not found.
error: failed processing manifest. -
Try:
> Run with --stacktrace option to get the stack trace.
> Run with --info or --debug option to get more log output.
> Run with --scan to get full insights.
> Get more help at https://help.gradle.org.
==============================================================================
2: Task failed with an exception.
-
What went wrong:
Execution failed for task ':app:bundleReleaseResources'.
> A failure occurred while executing com.android.build.gradle.internal.res.Aapt2ProcessResourcesRunnable
> Android resource linking failed
/home/builder/clone/build/app/intermediates/bundle_manifest/release/AndroidManifest.xml:74: error: resource string/facebook_client_token (aka app.kontnu.com:string/facebook_client_token) not found.
error: failed processing manifest. -
Try:
> Run with --stacktrace option to get the stack trace.
> Run with --info or --debug option to get more log output.
> Run with --scan to get full insights.
> Get more help at https://help.gradle.org.
==============================================================================
BUILD FAILED in 6m 1s
Running Gradle task 'bundleRelease'... 362.3s
Gradle task bundleRelease failed with exit code 1
Build failed :|
Step 8 script Build AAB with Flutter
exited with status code 1
Expected Behavior
Back to publishing on the Google Play store
Steps to Reproduce
- Test to deploy to Google Play
- See the failed views logs
Reproducible from Blank
- The steps to reproduce above start from a blank project.
Bug Report Code (Required)
ITFXjcmAvM9OmNhE7pP2b8JVoGQwGUAaU40V0t1ETRQbCIj4B+wyeODSXFZoZOazaH9qIlejqz8z3MKPiePfO/AoCE2qf7pxws9MERPPbFGjb7KQPpGKOnN6I9NVC1SB37TUsB1QHMxhWC0+712EH9i/Ej6Cf9qOYwx5e6fDbOY=
Visual documentation

Environment
- FlutterFlow version: v5.2.1 released February 14, 2025
- Platform: (Web, MacOS Desktop): Web
- Browser name and version: Chrome 132.0.6834.162
- Operating system and version affected: (desktop): macOS Sequoia 15.3
Additional Information
No response