How can I ask Gradle to ignore namespace issues ?

[TheCarpetMerchant]

I've just started to process to upgrade to 3.10, and have multiple packages that haven't update to gradle 8.
How can I go past that ? Because if it's not possible, I'll have to stay on 3.7 indefinitely. It makes no sense to cut myself off from all the packages that haven't upgraded and doing all the upgrading and testing myself is too big of a task.

[dam-ease]

Hi @TheCarpetMerchant. What packages are affected??

[TheCarpetMerchant]

Example : flutter_archive
But I'm using plenty of packages that haven't received an update in months or a year simply because there is no need to. For example wakelock will probably raise the same issue.

[TheCarpetMerchant]

Downgrading to Gradle 7.4.2 seems to work well, don't know why Flutter (or something else) asked me to upgrade.

[dam-ease]

Okay, can you share the error message or logs you are getting??

[TheCarpetMerchant]

Well, I didn't keep the whole error but here's some of it copy-pasted from a discord message :

A problem occurred configuring project ':flutter_archive'.
Could not create an instance of type com.android.build.api.variant.impl.LibraryVariantBuilderImpl.
Namespace not specified. Please specify a namespace in the module's build.gradle file like so:

     android {
         namespace 'com.example.namespace'
     }

     If the package attribute is specified in the source AndroidManifest.xml, it can be migrated automatically to the namespace value in the build.gradle file using the AGP Upgrade Assistant; please refer to https://developer.android.com/studio/build/agp-upgrade-assistant for more information.

[dam-ease]

Hi @TheCarpetMerchant. Per this #126403 (comment), this seems to have been fixed on the latest master channel. Can you confirm this by switching to the latest master?

[JycTheDev]

7.4.2

Hi @TheCarpetMerchant. Per this #126403 (comment), this seems to have been fixed on the latest master channel. Can you confirm this by switching to the latest master?

I am not sure it has been fixed on master branch because the issue is still there.

[dam-ease]

Hi @jbankz. Were you able to still reproduce the issue after following this #126403 (comment)