jeyasri
jeyasri

Reputation: 1

Execution failed for task ':app:processDebugResources'[flutter]

I am developing an flutter e-commerce app for both Android and IOS users. When I run my code, its shows an resource error, I couldn't find the answers.


* What went wrong:
Execution failed for task ':app:processDebugResources'.
> A failure occurred while executing com.android.build.gradle.internal.tasks.Workers$ActionFacade
   > Android resource linking failed
     C:\Users\JEYASRI.A\AndroidStudioProjects\flutter_foodapp\build\file_picker\intermediates\library_manifest\debug\AndroidManifest.xml:9:5-15:15: AAPT: error: unexpected element <queries> found in <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 47s
The built failed likely due to AndroidX incompatibilities in a plugin. The tool is about to try using Jetfier to solve the incompatibility.
Building plugin cloud_firestore...
Running Gradle task 'assembleAarRelease'...
Exception: The plugin cloud_firestore could not be built due to the issue above.```

Upvotes: 0

Views: 288

Answers (1)

Nibrass H
Nibrass H

Reputation: 2497

Please note that you are getting the following error:

 AAPT: error: unexpected element <queries> found in <manifest>.

The error is stating that the element is not being recognized by Android Gradle Plugin.

Android 11 introduced <queries> as a manifest element and older versions of the Android Gradle Plugin do not have this element.

So it could be that you are using an Android Gradle Plugin which does not allow the element.

There are some series of patch versions released by Google in order to fix this error (3.3.3, 3.4.3, 3.5.4, 3.6.4 and 4.0.1).

So please upgrade your build gradle version to one from the above list.

Android Studio 4.1 or higher, with a matching Android Gradle Plugin (e.g 4.1.* series) does recognize manifest element so they don't face these types of errors.

Have a look into the Android Developers Blog post.

Upvotes: 1

Related Questions