IssueTracker

Does it also make AndroidManifest.xml optional when not needed for library modules?

Yes, thanks, that's not supported yet, but that's within the scope of this bug.

In 7.0.0-alpha05 the AndroidManifest.xml file is required but you can omit the package declaration when namespace is defined through DSL.

The minimal valid manifest content is <manifest />.

Re: #2 and #3, I reopened Issue 156824500 to track supporting libraries without source manifests.

Before I open a separate bug, I followed the migration when updating to AGP 7.1.0, and it works generally but the Android Studio manifest editor shows the following in the merged tab.

Merging Errors: Error: Main AndroidManifest.xml at AndroidManifest.xml manifest:package attribute is not declared

This is with AS Chipmunk. Is this known issue, or expected in Chipmunk? Need a clean repro?

Re #6, which version of AS Chipmunk are you using? Beta 1?

ps - AFAIK, #6 is not a known issue

Thanks, I can raise a bug with an extracted repro if needed.

Android Studio Chipmunk | 2021.2.1 Canary 7
Build #AI-212.5457.46.2112.8043657, built on January 5, 2022

I'm able to repro. I'll file a separate bug and work on a fix. Thanks Yuri!

ps - I filed Issue 216640707 to track.

Please let me know if this should be a new issue but AGP 7.3 Beta1 warns about using package within the manifest xml even though we do not have a manifest file and are already using namespace

> Task :recyclerview-items:processReleaseManifest
package="com.careem.subscription.internal.recyclerview.items" found in source AndroidManifest.xml: /Users/Efe/Projects/Careem/subscription-sdk/android/recyclerview-items/build/intermediates/tmp/ProcessLibraryManifest/release/tempAndroidManifest2424595280278774479.xml.
Setting the namespace via a source AndroidManifest.xml's package attribute is deprecated.
Please instead set the namespace (or testNamespace) in the module's build.gradle file, as described here: https://developer.android.com/studio/build/configure-app-module#set-namespace
This migration can be done automatically using the AGP Upgrade Assistant, please refer to https://developer.android.com/studio/build/agp-upgrade-assistant for more information.

Notice the manifest file above is from the build directory.

Re #10, thanks, yes, that's a known issue that was fixed in time for AGP 7.3 beta 3; see Issue 231326529.

There seem to be some tangentially related issues like https://b.corp.google.com/issues/234613757

This may be a code bug requiring a fix in the project, but it isn't surfaced to the user. I'm pretty sure I've found a number of ways to trigger manifest merging failures, is there some way to surface these types of errors more obviously, or does this improve in AGP 7.4.x?

Re #12, thanks, I replied on Issue 234613757.

I'm pretty sure I've found a number of ways to trigger manifest merging failures, is there some way to surface these types of errors more obviously, or does this improve in AGP 7.4.x?

Can you elaborate on the specify ways?

Not, I was sort of treating them as all related. Another one is https://b.corp.google.com/issues/230475547

Re: #15, can you add more details so I can reproduce? What version of Android Gradle plugin are you using?

Re #17, that looks like Issue 232060575.

As of Android Gradle plugin version 8.0.0-alpha03, namespace is required to be set via the DSL.

Re: #20, can you give more details (error message, repro instructions, etc.)? You can file a separate bug and link it on this thread.

So, I'm not able to migrate from Gradle 7.x to 8.x on Flutter project.

If you add the matching namespace DSL to each sub-module's build.gradle file (it must match the value of the package attribute in the manifest), then there shouldn't be a problem.